Separate the Manual client into its own apworld

[FuzzyGamesOn]

So, this idea started from this line of problems related to AP manifest things:

• Our current solution for broken clients is asking people to put the stable release of Manual in their custom_worlds.
• We don't want to add a manifest file to the stable release because it can cause misreporting of games built on it (when they don't update that manifest).
• Without a manifest file, the stable release apworld won't load the client, rendering the first bullet's solution ineffective.

But also relates to this problem:

• A lot of Manual creators don't update from recent versions. This typically breaks the client only.

---

So! This PR aims to separate the Manual Client into its own src folder, with the goal of releasing it as a separate apworld alongside the stable template apworld. That way, when people need to update their client, they can just... update that.

And the client apworld can have a manifest file because no one is extending it. If they want to make their own custom client, they can just package it with their apworld as normal.

Making this a draft for now. This PR is also incomplete until it includes workflow changes to do both:

• Generating the manifest file for the client, likely as a copy of the Manual manifest template like other worlds would
• Packaging the new client src folder as an apworld and add that to release artifacts for both release workflows