2.2.1: Improve Aspire HTTP integration (#15)

Motivation
----------
Better functionality and consistency with Aspire patterns.

Modifications
-------------
- Allow passing in a specific endpoint or endpoint selector
- Allow choosing the HttpClientName from the IHttpClientFactory
- Allow customizing the path to the application state endpoint
- Use WithHttpCommand to add the commands
- Disable the start command when the service is not running
- Reset the current status if the service is restarted
- Add an Aspire testing app host
- Add OpenTelemetry and a health check to the test web app for Aspire compatibility and enable HTTPS in the launch configuration

Results
-------
- Callers may pick the endpoint in a variety of ways rather than only endpoint name
- The HTTPS endpoint is now prefered by default, and all selection rules used by WithHttpCommand in Aspire are used
- Requests use the Aspire HTTP client factory and get dev certificate trust from Aspire, and the client factory may be customized
- Consumers using a custom URL instead of /applicationstate may match this configuration this in Aspire
- Shawarma commands remain disabled if the service is stopped and get the proper state if the service is restarted

2.2.0

What's Changed

• Modernize to a minimum of .NET 8 and C# 14 by @brantburnett in #13
• Add library to easily use Shawarma from Aspire by @brantburnett in #14

Full Changelog: 2.1.0...2.2.0

2.1.0

What's Changed

• Move to .NET 6 with 3.1 backward compat (ARCH-108) by @brantburnett in #5
• Add ActiveServices to ApplicationState (ARCH-110) by @brantburnett in #6
• Use source gen serializers (ARCH-111) by @brantburnett in #7
• Improve documentation by @brantburnett in #8
• Support trimming (ARCH-112) by @brantburnett in #9
• Mark middleware approach as obsolete by @brantburnett in #10
• Improve Content-Type handling by @brantburnett in #11

Full Changelog: 2.0.1...2.1.0

Switch to System.Text.Json for serialization

Switch to System.Text.Json serialization (SWS-4542) (#4)

Motivation
----------
Better alignment with .NET Core 3.1 and .NET 5. They currently use this
as the default, so we can avoid pulling in Newtonsoft.Json. Also, the
synchronous stream rendering causes problems without specific config
being in place in the app startup code.

Modifications
-------------
Drop Newtonsoft.Json and serialization settings from Abstractions.

Switch AspNetCore to use System.Text.Json, adding it as a dependency for
.NET Standard 2.0 only. Make serialization and deserialization async.

https://centeredge.atlassian.net/browse/SWS-4542

Support for endpoint routing in .NET 5 and .NET Core 3.1

 Update for .NET 5 and endpoint routing (SWS-4370) (#2)

Motivation
----------
Better integration with modern frameworks.

Modifications
-------------
Multi-target for various frameworks, and on the supported frameworks add
support for endpoint routing.

Upgrade various NuGet packages and the C# language version.

Update the README to show endpoint routing.

https://centeredge.atlassian.net/browse/SWS-4370

Initial Release

Move abstractions to separate package (PHNX-2997) (#1)

Motivation
----------
Allow packages which want to consume some Shawarma features to do so
without depending on the entire dependency tree.

Move to abstractions assembly

Move abstractions to separate package (PHNX-2997) (#1)

Motivation
----------
Allow packages which want to consume some Shawarma features to do so
without depending on the entire dependency tree.

Initial Test

1.0.0-alpha001

Add .travis.yml