Re-instate old methods, but as obsolete

[matt-richardson]

Description

Release 111.0.0 broke a few scenarios, with the changes in #2078 and #2141.

While both of these changes are valuable, they are breaking changes, and they break code generated by https://github.com/OpenAPITools/openapi-generator.

Purpose

This pull request is a:

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

This PR adds overloads to these methods to re-instate the old behaviour, but flags them as [Obsolete].
(If projects that consume this library has <TreatWarningsAsErrors>true</TreatWarningsAsErrors> in the csproj, then this can be overridden via <<NoWarn>618</NoWarn>)

Checklist

• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

[alexeyzimarev]

Nice! Please accept the CLA and I'll merge it.

[alexeyzimarev]

@matt-richardson 👆 could you please do this? it's a requirement for new contributors from .NET Foundation.

[matt-richardson]

@matt-richardson 👆 could you please do this? it's a requirement for new contributors from .NET Foundation.

Hi @alexeyzimarev. I'm just waiting for company sign off... It's taking longer than I'd like :(

[matt-richardson]

@dotnet-policy-service agree company="Octopus Deploy"

[matt-richardson]

@matt-richardson 👆 could you please do this? it's a requirement for new contributors from .NET Foundation.

Hi @alexeyzimarev. I'm just waiting for company sign off... It's taking longer than I'd like :(

Sorry for the delay - all sorted now!

[matt-richardson]

Thanks for merging and releasing, @alexeyzimarev! Appreciate your work!