Fix missing BaseAddress on OData HttpClient

[Mikeoso]

Summary

• Set HttpClient.BaseAddress from ODataSettings.Url during OData client registration
• PanoramicData.OData.Client passes relative URIs to HttpClient.SendAsync internally, which requires BaseAddress to be set — without it, an InvalidOperationException is thrown at runtime

Test plan

• dotnet build passes (0 errors)
• All 220 tests pass
• Verify OData calls succeed in consumer project (INW.Integration.COOR)

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR updates the OData client DI registration to set HttpClient.BaseAddress from ODataSettings.Url, preventing runtime InvalidOperationException when the PanoramicData OData client sends relative URIs.

Changes:

• Set HttpClient.BaseAddress during OData client registration based on ODataSettings.Url.

Comments suppressed due to low confidence (2)

IntegratoR.OData/Common/Extensions/ApplicationDependencyInjection.cs:122

• HttpClient.BaseAddress URI resolution is sensitive to a trailing slash. With a configured URL like https://.../data (no trailing /, as used in tests), resolving a relative request URI like $metadata or Customers will drop the data segment and produce https://.../$metadata / https://.../Customers. Consider normalizing BaseAddress to ensure it ends with / (and keep ODataClientOptions.BaseUrl consistent) so relative OData paths stay under the intended /data/ endpoint.

            httpClient.BaseAddress = new Uri(settings.Url);

            var options = new ODataClientOptions
            {
                BaseUrl = settings.Url,
                HttpClient = httpClient

IntegratoR.OData/Common/Extensions/ApplicationDependencyInjection.cs:123

• This change introduces important runtime behavior (ensuring relative URIs can be sent via HttpClient), but there’s no unit test asserting the ODataClient’s underlying HttpClient has a BaseAddress set (or that a relative request no longer throws InvalidOperationException). Consider adding a focused DI test that resolves ODataClient and verifies it can issue a relative request without throwing (using a fake HttpMessageHandler), to prevent regressions.

            httpClient.BaseAddress = new Uri(settings.Url);

            var options = new ODataClientOptions
            {
                BaseUrl = settings.Url,
                HttpClient = httpClient
            };

[Copilot]

new Uri(settings.Url) will throw (UriFormatException/ArgumentNullException) if ODataSettings.Url is empty or malformed. Since ODataSettings.Url defaults to string.Empty and there’s no options validation in this registration path, consider validating with Uri.TryCreate(..., UriKind.Absolute, out var uri) and throwing a clearer configuration error (e.g., indicating ODataSettings:Url must be a valid absolute URL).