feat: allow using mockaco on aspnet core apps

[gomete]

Closes #88

Hi @natenho!

These are the changes that I did to use Mockaco in an ASP.NET Core app:

• We have created a new package Mockaco.AspNetCore with the main logic, extracting the dependency injection and configuration of endpoints.
• We have added a new way of changing the configuration that fits better with an ASP.NET Core app but maintaining the previous way of configuring it.
• We have migrated it to .NET 6 as it is LTS.
• We have moved the VerifyController to use .MapGet to avoid the conditional MapWhen and avoid making it public, so it is not part of the API of the package.
• We have added the package Microsoft.CodeAnalysis.PublicApiAnalyzers so it is easy to identify which parts of the package are public and to detect breaking changes.
• We have made internal all the classes that potentially can be internal. The rest of them are public because of Microsoft.CodeAnalysis.CSharp.Scripting.
• It is compatible with the current standalone Mockaco. We have added some Postman tests to ensure that at least the examples are still working as expected. The Postman tests test/_postman/Mockaco.postman_collection.json and the script checkBuild.ps1 can be removed once you tested the change. We only used them to ensure that the build, the unit tests and the Docker build will work.
• We have tested adding a controller and an additional MapGet to the existing ASP.NET Core using Mockaco to check that it is using the controller/MapGet instead of using Mockaco. In case there is no match in the existing controllers, it is handled by Mockaco.

[natenho]

Well that is a big PR!! It's indeed an awesome feature!
Thank you for your time, I'm glad that you are interested to contribute to the project! I'll be reviewing everything here soon ;-)

[gomete]

Hi @natenho, did you have the chance to review this?

[natenho]

Hi @gomete, I apologize the delay. A few days ago I had to fix a bug and I was working on integrating this PR #87, where I noticed some points that needs some improvement before merging. My plan is to merge #87 and your PRs would be the next ones. I would appreciate if you could integrate the current master branch into your code until there.

Anyway, I did not forget your PRs, hang tight! ;)

[gomete]

Hi @natenho, thanks for the quick response! I will solve the conflicts this afternoon.