[tracy] Update to 0.14.0

[Niels Eppenhof (nepp95)]

• Changes comply with the maintainer guide.
• SHA512s are updated for each updated download.
• The "supports" clause reflects platforms that may be fixed by this new version, or no changes were necessary.
• Any fixed CI baseline and CI feature baseline entries are removed from that file, or no entries needed to be changed.
• All patch files in the port are applied and succeed.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Exactly one version is added in each modified versions file.

Update: https://github.com/wolfpld/tracy/releases/tag/v0.14.0

[Niels Eppenhof (nepp95)]

Niels Eppenhof (Niels Eppenhof (@nepp95)) please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree

[Niels Eppenhof (nepp95)]

Builds failed on a version difference of md4c when using the gui-tools feature. Tracy updated to a pinned commit (newer release tag of md4c isn't there). Currently md4c is pulled in using vcpkg (in the port) but the newest version available is outdated, added PR that this now requires before builds will succeed: #53408

Alternative would be pulling in the source manually, but I imagine this is preferable. Tested locally with x64-windows triplet.

[Niels Eppenhof (nepp95)]

I seem to have hit the jackpot on my first PR's.

Tracy released 0.14.0 and since I actively use it myself and prefer vcpkg, I'd thought I'd give a hand and update the vcpkg port. 0.14.0 comes with a lot of changes and they restructured their build system quite a bit but I tried to keep the port as much as it was. The only remaining issue seems to be md4c, which I hadn't realized gets used by quite a few important packages (qt5-base for example).

md4c has gotten a few API breaking changes but hasn't put out a new release in the meantime. Tracy 0.14.0 circumvents this by pinning a commit (line 240), which contains some of those breaking changes. Since the tracy port uses find_package instead of CPM, md4c resolves to the older 0.5.3 release tag which does not contain those changes. Updating the baseline so find_package resolves the right version breaks other packages and as far as I could find in the maintainer guide that kind of versioning isn't preferred.

So I could fix the PR in multiple ways, but since it is my first PR here, I'd like to know what the preferred way is as to not make a mess of it;

• Update baseline to the pinned commit with a date version for md4c and fix the broken packages in Update md4c #53408
• Keep the PR but don't update the baseline, pin the version-date in tracy.
• Pull in the source locally for tracy with vcpkg_from_github, no other PR's.