Remove unavailable modules

[KyrietS]

What does this PR do?

Removes links to modules resulting with 404.

I wonder if it would be better to link @Jarod42's fork instead of the original CMake module. As far as I know, the fork fixes several bugs?

Did you check all the boxes?

• Focus on a single fix or feature; remove any unrelated formatting or code changes
• Add unit tests showing fix or feature works; all tests pass
• Mention any related issues (put closes #XXXX in comment to auto-close issue when PR is merged)
• Follow our coding conventions
• Minimize the number of commits
• Align documentation to your changes

You can now support Premake on our OpenCollective. Your contributions help us spend more time responding to requests like these!

[KyrietS]

Poking @Enhex for reference as he's the author of the premake-cmake module.

[Enhex]

Note that I'm not actively maintaining the CMake generator.
I experimented with several IDEs on Linux and wrote Premake generators to try them, and now I
only maintain generators I use.

So maybe there's a fork of my repo that's more active, in which case it should be referred to instead.

[Jarod42]

On my side, I created generic integration tests for Premake's generators, and just testing the generators which seems important (as CMake's one).
I indeed fix those which fail my tests (and create PRs) (Authors of premake-ninja even gave me rights to modify repository directly).
Whereas I might fix issues encountered with my tests, I don't think I will go further for my forks.

[KyrietS]

Alright, considering both statements I decided to link @Jarod42's fork. It has a few more features, and the original repo is tagged on GitHub anyway. This list is very "community driven" and neither of you should feel obligated to maintain these modules ofc.