[sfml] Update SFML to 3.0.0

[eXpl0it3r]

Fixes #43000

• 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.
• Any fixed CI baseline entries are removed from that file.
• Any patches that are no longer applied are deleted from the port's directory.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is added to each modified port's versions file.

---

This updates SFML to the recently released 3.0.0 version.

• Deindex Thor: [thor] Deindex. #43067
• Update SFGUI to SFML 3: Upgrade to SFML 3 TankOs/SFGUI#100
• Release new SFGUI version
• Update imgui-sfml: SFML/imgui-sfml@734e627
• Release new imgui-sfml version

[eXpl0it3r]

Looks like we need to limit SFML usage to SFML 2.x, until the packages are updated.

• SFGUI
• Imgui-SFML
• Thor

I tried to understand versioning, but don't fully understand it. Can someone give me a hint, how one would for example limit Thor to SFML 2.* (or even better SFML 2.5 and later SFML 2.* versions)?

[alvarogalloc]

Can SFML ship the in vcpkg like SDL? In SDL there are ports for all three major versions. If this happens to SFML, maybe as the new release is adapted to dependent packages (e.g. thor, imgui-SFML, etc.), they can be released as feature variants of the existing ones (e.g. imgui-sfml[sfml3])

[eXpl0it3r]

The guide says that one shouldn't create new ports for different versions (i.e. sfml2 & sfml3). So I guess that would be a question for @BillyONeal or similar.

[BillyONeal]

The guide says that one shouldn't create new ports for different versions (i.e. sfml2 & sfml3). So I guess that would be a question for @BillyONeal or similar.

Can they be installed side-by-side without stomping on each other?

[ChrisThrasher]

https://github.com/SFML/imgui-sfml/releases/tag/v3.0

ImGui-SFML 3 has been released which targets SFML 3