Update mcr.microsoft.com/mssql/server Docker tag to v2022

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
mcr.microsoft.com/mssql/server	service	major	2019-latest -> 2022-latest

---

Configuration

📅 Schedule: Branch creation - "before 5am on Sunday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[Piedone]

Do we want to update these, @sebastienros, or rather keep to what YesSql also uses? Also see #17184 and #17183.

[sebastienros]

what YesSql also uses

I don't think that's related to yessql, more about what version we want to test OC against. Ideally we would test on all the supported versions, I assume 2019 is the lowest (because of yessql). 2022 is the latest. I'd keep the lowest to be certain we are not changing something to a newer syntax that is not supported in 2022.

[Piedone]

Yeah, that's why I'm asking: YesSql supports 2019, and since OC accesses the DB only via YesSql, IMO it should also support that as the lowest common denominator. Keeping to the versions in https://github.com/sebastienros/yessql/blob/main/.github/workflows/build.yml, then, which are the versions we currently use. Closing the PRs.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 2022.x releases. But if you manually upgrade to 2022.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.