Updated expired UI Test certificate. Expires 9/8/2023.

[Arlodotexe]

Fixes #4759

PR Type

What kind of change does this PR introduce?

What is the current behavior?

What is the new behavior?

PR Checklist

Please check if your PR fulfills the following requirements:

• Created a feature/dev branch in your fork (vs. submitting directly from a commit on main)
• Based off latest main branch of toolkit
• Tested code with current supported SDKs
• New component
  • Pull Request has been submitted to the documentation repository instructions. Link:
  • Added description of major feature to project description for NuGet package (4000 total character limit, so don't push entire description over that)
  • If control, added to Visual Studio Design project
• Sample in sample app has been added / updated (for bug fixes / features)
  • Icon has been created (if new sample) following the Thumbnail Style Guide and templates
• New major technical changes in the toolkit have or will be added to the Wiki e.g. build changes, source generators, testing infrastructure, sample creation changes, etc...
• Tests for the changes have been added (for bug fixes / features) (if applicable)
• Header has been added to all new source files (run build/UpdateHeaders.bat)
• Contains NO breaking changes

[ghost]

Thanks Arlodotexe for opening a Pull Request! The reviewers will test the PR and highlight if there is any conflict or changes required. If the PR is approved we will proceed to merge the pull request 🙌

[michael-hawker]

You also need to update the package identity strings in the UI Test cs file, see here: https://github.com/CommunityToolkit/WindowsCommunityToolkit/pull/4752/files#diff-0b322e99a0407123781aa69647ae087fef5cb2c536ba9ef787bbf8461838a37d (there my be others, do a quick search)

[ghost]

This PR has been marked as "needs attention 👋" and awaiting a response from the team.

[Arlodotexe]

We should squash this one

[michael-hawker]

Ah, suppose I should try running locally in VS as well to be sure. But I think the changes should be fine. If they run in TAEF in the CI then they should run locally from the commandline as well. (And don't remember if TAEF is the only one that needs the cert anyway.)

[Arlodotexe]

Needs 1 more approving review, or an admin override. This PR unblocks several other PRs.