Bump System.Composition.AttributedModel and 2 others

Bumps System.Composition.AttributedModel from 6.0.0 to 10.0.9
Bumps System.Composition.Hosting from 6.0.0 to 10.0.9
Bumps System.Composition.TypedParts from 6.0.0 to 10.0.9

---
updated-dependencies:
- dependency-name: Microsoft.CodeAnalysis.CSharp.Analyzer.Testing
  dependency-version: 1.1.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: system
- dependency-name: System.ComponentModel.Composition
  dependency-version: 10.0.9
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: system
- dependency-name: System.Composition.AttributedModel
  dependency-version: 10.0.9
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: system
- dependency-name: System.Composition.Hosting
  dependency-version: 10.0.9
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: system
- dependency-name: System.Composition.TypedParts
  dependency-version: 10.0.9
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: system
- dependency-name: System.Formats.Asn1
  dependency-version: 10.0.9
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: system
...

Signed-off-by: dependabot[bot] <support@github.com>

🖉 Update changelog with untagged-82c31839570064d4052c

Repurpose older [Service<T>] to allow specifying a service type

We add an analyzer that will flag the previous usage as an error (requiring the removal of the T or setting it to the actual service to register). This should prevent bumps and rebuilds without notice.

Since the attributes don't have run-time impact but are rather purely compile-time, bumping but not building (i.e. via a transitive dependency, say or direct copying), would not cause runtime failures because the registrations in the previously compile assembly would remain as they were.

This unlocks a very useful scenario to trim down the amount of registered interfaces.

Fixes #281

Bump Microsoft.CodeAnalysis.CSharp.Workspaces from 4.13.0 to 4.14.0

---
updated-dependencies:
- dependency-name: Microsoft.CodeAnalysis.CSharp.Workspaces
  dependency-version: 4.14.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

⬆️ Bump files with dotnet-file sync

⬆️ Bump files with dotnet-file sync

Bump minor dependencies

Bump the tests group with 3 updates

Bumps the tests group with 3 updates: [Microsoft.NET.Test.Sdk](https://github.com/microsoft/vstest), [xunit](https://github.com/xunit/xunit) and [xunit.runner.visualstudio](https://github.com/xunit/visualstudio.xunit).


Updates `Microsoft.NET.Test.Sdk` from 17.9.0 to 17.13.0
- [Release notes](https://github.com/microsoft/vstest/releases)
- [Changelog](https://github.com/microsoft/vstest/blob/main/docs/releases.md)
- [Commits](microsoft/vstest@v17.9.0...v17.13.0)

Updates `xunit` from 2.7.0 to 2.9.3
- [Commits](xunit/xunit@v2-2.7.0...v2-2.9.3)

Updates `xunit.runner.visualstudio` from 2.5.7 to 3.0.2
- [Release notes](https://github.com/xunit/visualstudio.xunit/releases)
- [Commits](xunit/visualstudio.xunit@2.5.7...3.0.2)

---
updated-dependencies:
- dependency-name: Microsoft.NET.Test.Sdk
  dependency-version: 17.13.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: tests
- dependency-name: xunit
  dependency-version: 2.9.3
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: tests
- dependency-name: xunit.runner.visualstudio
  dependency-version: 3.0.2
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: tests
...

Signed-off-by: dependabot[bot] <support@github.com>

Don't emit registrations with generics that don't satisfy constraints

We were emitting instantiations of generic interfaces (implemented by the service) for covariant type parameters that didn't satisfy the generic type parameter constraints.

Don't report inconsitencies if lifetimes match

We automatically deduplicate service registrations that are exactly the same, so we don't need to report that case.