chore: Updated dependencies and regenerated recipes

[michalChrobot]

Purpose of this PR

This PR addresses 2 things pointed by renovate bot

1. It updates dependencies on Wrench and RecipeEngine.API and regenerates recipes
2. It updates minimal editor and dependencies for testproject-tools-integration, testproject and minimalproject
3. It updates minimal editor supported by NGO package

More important is second point so first of all note that 2021.3 xLTS will be out of support in 6 days so I wanted to use this moment to update minimal editor (only relevant for NGOv1.X and develop branch) to 2022.3 for all our test projects and package.

For the package I updated minimal supported editor to 2022.3 and updated dependencies to the ones on that version. I included Changelog mention of this. Note that in that case release automation will be triggered (changelog not empty) but I think we can still release this patch version even if with only that change

For the projects I used 2022.3.61f1 editor, I updated few dependencies and opened the projects so this involves automatic bumping of some dependencies detected by editor manifest

Jira ticket

N/A

Changelog

• Changed: Changed minimum Unity version supported to 2022.3 LTS

Documentation

N/A

Testing & QA (How your changes can be verified during release Playtest)

N/A

Backports

This is a partial backport of #3704

[michalChrobot]

@NoelStephensUnity @EmandM I also removed all testing on 2021 editor and bumped NGO version to 1.15.0 due to Vetting test suggestion of

The Unity version requirement is more strict than in the previous version of the package. Increment the minor version of the package to leave patch versions available for previous version. Read more about this error and potential solutions at https://docs.unity3d.com/Packages/com.unity.package-validation-suite@latest/index.html?preview=1&subfolder=/manual/package_unity_version_validation_error.html#the-unity-version-requirement-is-more-strict-than-in-the-previous-version-of-the-package

And the fact that this bumps dependencies by minor version

[michalChrobot]

After some thinking I would actually argue that if this is the only change in the package (NGOv1.X) for now then I wouldn't do the release here since it doesn't provide any meaningful value to users

I will add some exception to release automation that if this is the only thing in the changelog then we shouldn't run the automation

*I modified it and verified locally that it works

[michalChrobot]

One more question @NoelStephensUnity @EmandM

After doing those changes I got the following "breaking changes" error. Do you know if this relates to transport version bump OR editor version bump?