feat: Include the container name in the reuse hash

[0xced]

What does this PR do?

This pull request removes the [JsonIgnore] attribute from the ContainerConfiguration.Name property so that the container name becomes part of the reuse hash.

Why is it important?

The rationale behind this change is explained in #1161.

Important

Changing the parts used in the reuse hash will break existing reused containers but the best time to do it is now, while the reuse feature is still at the experimental stage.

Related issues

Closes #1161

How to test this PR

A new unit test (ContainersWithDifferentNamesShouldHaveDifferentHashes) has been added.

[netlify]

✅ Deploy Preview for testcontainers-dotnet ready!

Name	Link
🔨 Latest commit	d715a18
🔍 Latest deploy log	https://app.netlify.com/sites/testcontainers-dotnet/deploys/662b55eb7bf3d1000850f66e
😎 Deploy Preview	https://deploy-preview-1162--testcontainers-dotnet.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[HofmeisterAn]

I do not remember, but I thought this was on purpose. However, I think excluding it does not make much sense. IIRC when we initially discussed the feature, we were considering hashing the container response from the Docker Engine API (which contains random names). Nevertheless, LGTM. Could you please update the documentation accordingly?

testcontainers-dotnet/docs/api/resource_reuse.md

Lines 20 to 29 in f6c93d3

	- [ContainerConfiguration](https://github.com/testcontainers/testcontainers-dotnet/blob/develop/src/Testcontainers/Configurations/Containers/ContainerConfiguration.cs)
	- Image
	- Entrypoint
	- Command
	- Environments
	- ExposedPorts
	- PortBindings
	- NetworkAliases
	- ExtraHosts
	- Labels

[0xced]

Could you please update the documentation accordingly?

Of course! I just pushed d715a18 which updates the documentation.