Change into Plugin Repository

[npruehs]

I'd like to suggest to use multiple (feature/bugfix) branches and issue multiple PRs. We probably don't want to merge all 29 commits (yet). For instance:

• Changing the repository into a plugin repository is a great idea (and has been suggested before), but - where's the example gone? Many people have found that example pretty helpful for setting up their own project.
• Adding GameplayAbilities is one way to go about providing a more sophisticated combat system, but I think we should at least have an extensive discussion about this. Adding dependencies can be a big deal, and GameplayAbilities is a pretty big dependency, which Epic Games has repeatedly flagged as "subject to major changes".

On the other hand, many of the smaller commits sound very useful, and I'd love to merge them!

[Mephiztopheles]

I didn't know that all my commits would be added to this one PR.

• The Example would go into a different Repository. And the other Repository would show how to add the plugin aswell to the plugins folder as a submodule. Of yourse I don't want to remove all these helpful example assets and BPs.
• I didn't know, that the GA was subject to major changes. But imho it's very useful and a good base for adding other abilities. Maybe this could be an extension or a different branch

Do you have an idea how to approach this so we can have beautifully small merged PRs?

[Mephiztopheles]

Maybe you want to rename the Repository also to "RealTimeStrategy", so it matches the name of the plugin