Fix Umbraco.Tests.Common warnings.

[jbreuer]

Prerequisites

• I have added steps to test this contribution in the description below

Issue: #15015

Description

This PR fixes the following task:

Warnings in Umbraco.Tests.Common.

This PR can be tested by building the Umbraco source code and checking that this warnings for Umbraco.Tests.Common are gone.

[github-actions]

Hi there @jbreuer, thank you for this contribution! 👍

While we wait for one of the Core Collaborators team to have a look at your work, we wanted to let you know about that we have a checklist for some of the things we will consider during review:

• It's clear what problem this is solving, there's a connected issue or a description of what the changes do and how to test them
• The automated tests all pass (see "Checks" tab on this PR)
• The level of security for this contribution is the same or improved
• The level of performance for this contribution is the same or improved
• Avoids creating breaking changes; note that behavioral changes might also be perceived as breaking
• If this is a new feature, Umbraco HQ provided guidance on the implementation beforehand
• 💡 The contribution looks original and the contributor is presumably allowed to share it

Don't worry if you got something wrong. We like to think of a pull request as the start of a conversation, we're happy to provide guidance on improving your contribution.

If you realize that you might want to make some changes then you can do that by adding new commits to the branch you created for this work and pushing new commits. They should then automatically show up as updates to this pull request.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[jbreuer]

When I created this PR there weren't any merge conflicts. Not sure what happend.

[mikecp]

Hi @jbreuer ,

Thanks for providing the fix for this issue 👍
Someone from the core collaborators team will have a look at it soon.

Regarding the merge conflicts, I think your PR was more or less created at the same time as the release of V15 RC, which was merged into the contrib branch after your PR, hence possibiy creating the conflict... Or something like that 😅