Enhance server creation logic and add unit tests

[Mahdigln]

Fix port omission from BaseUrl in V2 server deserialization
Problem
When setting a BaseUrl with a non-standard port and the OpenAPI V2 document doesn't contain any server definitions, the port number was being omitted from the default server URL.
Example:
• Input: BaseUrl = "http://demo.testfire.net:8080"
• Current behavior: Server URL = "http://demo.testfire.net" ❌
• Expected behavior: Server URL = "http://demo.testfire.net:8080" ✅
Root Cause
The MakeServers method in OpenApiDocumentDeserializer.cs was using UriComponents.NormalizedHost which only extracts the hostname without the port number.
Solution
Changed UriComponents.NormalizedHost to UriComponents.Host | UriComponents.Port to preserve port information when extracting host details from the BaseUrl. This approach is consistent with the existing pattern used in OpenApiDocument.WriteHostInfoV2.
Additionally, fixed the early return logic to allow server creation from BaseUrl even when no host, basePath, or schemes are defined in the document.
Changes

1. src/Microsoft.OpenApi.Readers/V2/OpenApiDocumentDeserializer.cs:
   • Line 154: Changed from UriComponents.NormalizedHost to UriComponents.Host | UriComponents.Port
   • Line 144: Modified early return condition to check for defaultUrl != null
2. test/Microsoft.OpenApi.Readers.Tests/V2Tests/OpenApiServerTests.cs:
   • Added 3 new test cases to verify port preservation in various scenarios
   Testing
   • All existing tests pass ✅
   • Added comprehensive test coverage for port preservation scenarios
   • 16/16 OpenApiServerTests passing
   • 78/78 V2Tests passing
   FixesWhen BaseUrl has a port, the default server url doesn't contain the port #1294

[Vincent Biret (baywet)]

Thanks for the contribution!

Here are a few comments to help drive this forward.

[Vincent Biret (baywet)]

Thank you for making the changes!
An additional minor comment and I think we'll be ready to merge.
I'd like the v2 PR to be updated and ready to go before we merge this one.

[Vincent Biret (baywet)]

Thank you for making the changes!

Can you stand up a PR for v2/main branch please before we can merge everything?

[Mahdigln]

Thank you for making the changes! An additional minor comment and I think we'll be ready to merge. I'd like the v2 PR to be updated and ready to go before we merge this one.

Thank you! I've applied the changes

[Mahdigln]

Thank you for making the changes!

Can you stand up a PR for v2/main branch please before we can merge everything?

Sure! I'll create a separate PR for the v2/main branch.

[Mahdigln]

Thank you for making the changes!
Can you stand up a PR for v2/main branch please before we can merge everything?

Sure! I'll create a separate PR for the v2/main branch.

I'm unable to create a pull request directly from the main branch - it seems I don't have the necessary permissions or there's a branch protection rule.

[Mahdigln]

Vincent Biret (@baywet)

Hi
I noticed that the CLA check hasn’t been marked as signed on this PR.
However, I already signed the CLA before (on my previous pull request that was merged).
Could you please check why it’s not recognized this time, or let me know how I can re-confirm it?
Thanks a lot!

[Vincent Biret (baywet)]

@microsoft-github-policy-service rerun

[Vincent Biret (baywet)]

@mahdigIn the CLA issue is fixed, sometimes it fails for random reasons.

Just to clarify my ask:

1. create a branch from main
2. apply the code changes to that branch
3. create a pull request from that branch to main

You'll need to be working on a branch from your fork for this, like you've done for the v1 patch.

Let me know if you have any additional comments or questions.

[Mahdigln]

@mahdigIn the CLA issue is fixed, sometimes it fails for random reasons.

Just to clarify my ask:

1. create a branch from main
2. apply the code changes to that branch
3. create a pull request from that branch to main

You'll need to be working on a branch from your fork for this, like you've done for the v1 patch.

Let me know if you have any additional comments or questions.

Thank you very much for your help and clarification. 🙏
I’ve created a branch from main, applied the changes, and opened the pull request as you suggested.
I really appreciate your time and support