Update SharpYaml package to version 2.5.1

[johnthcall]

References

Upgrading Microsoft.OpenApi packages to a version which takes SharpYalm 2.1.5 with the following fix xoofx/SharpYaml#130

Submitter checklist

• Recommended: Join WireMock Slack to get any help in #help-contributing or a project-specific channel like #wiremock-java
• The PR request is well described and justified, including the body and the references
• The PR title represents the desired changelog entry
• The repository's code style is followed (see the contributing guide)
• Test coverage that demonstrates that the change works as expected
• For new features, there's necessary documentation in this pull request or in a subsequent PR to wiremock.org

[johnthcall]

@StefH the following change was introduced in the latest Microsoft.OpenApi.YamlReader microsoft/OpenAPI.NET#3027 which added limits MaxAliasExpansionNodeCount. This can be overridden when creating OpenApiYamlReader in the constructor of WireMockOpenApiParser. WireMockOpenApiParserTests.FromText_UsingYaml_ShouldReturnMappings requires increasing the AliasExpansionNodeCount from 5k to over 100k. Should WireMockOpenApiParser take a nullable OpenApiYamlReaderSettings or integer MaxAliasExpansionNodeCount to allow customers to increase this? Or should I revert the PR to just be the SharpYaml version increase?

[StefH]

Yes please keep it to sharpyml.

[StefH]

@johnthcall

Why would the AliasExpansionNodeCount be need to increased from 5k to over 100k?

5000 sounds a lot to me ?

[StefH]

It seems 1 million is needed for that example...

[StefH]

StefH/RamlToOpenApiConverter#30

[StefH]

StefH/RamlToOpenApiConverter#29

[StefH]

#1505