Move the development apps to there own project and load them in dyna…

[mrlux]

…mically

Breaking change

Proposed change

I think adding a development/debug/demo in the main repo is a very nice addition.
Here I made a change to move this development/debug code to its own project so it does not "pollute" the main code base.
The only link is a reference from the Service project to the NetDaemon.DevelopmentApps.csproj.
I do need to load the Assemblies in from the bin folder because dotnet does not load the bin dll's if there is no code reference (using NetDaemon.DevelopmentApps ...) somewhere in the Service project with would beat the purpose of separating the apps.
If you agree the dev.md will still need to be updated.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the [development checklist][dev-checklist]
• The code compiles without warnings (code quality chek)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io