Fix nullable tests

[RubenCerna2079]

Why make this change?

This change solves issue #3636

What is this change?

• Removed the ? symbol from the testing variables in order to allow the project to build properly inside the pipeline

How was this tested?

• Integration Tests
• Unit Tests
• Manual Tests

Manually ran the pipeline to ensure that it builds appropriately.

Sample Request(s)

N/A

[Copilot]

Pull request overview

Fixes build failures in test projects related to nullable reference type usage, addressing issue #3636 by aligning test code with each test project’s nullable configuration.

Changes:

• Removed nullable reference annotations (e.g., string?) from Service.Tests unit tests to match that project’s nullable-disabled compilation settings.
• Updated Cli.Tests helper entity creation to avoid passing null into non-nullable EntityGraphQLOptions constructor parameters.
• Adjusted a Cli.Tests end-to-end assertion to satisfy nullable analysis for DataSource.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
src/Service.Tests/UnitTests/SqlQueryExecutorUnitTests.cs	Removes nullable reference annotations in test parameters/helpers to avoid nullable-annotation compilation warnings/errors.
src/Service.Tests/UnitTests/RequestParserUnitTests.cs	Removes nullable reference annotations in local/test parameters consistent with nullable-disabled test project settings.
src/Service.Tests/Configuration/RuntimeConfigLoaderTests.cs	Removes nullable reference annotations for env-var locals to avoid nullable-annotation compilation warnings/errors.
src/Cli.Tests/ValidateConfigTests.cs	Replaces null GraphQL singular/plural with string.Empty to satisfy non-nullable EntityGraphQLOptions constructor.
src/Cli.Tests/EndToEndTests.cs	Uses null-forgiving operator for DataSource when asserting connection string under nullable-enabled compilation.