Add check for pester v5 - LastFullBackup

[jpomfret]

LastFullBackup

Changes

Do we think this is acceptable, in the new world if you set this config to $true you won't see the readonly databases that got skipped in the output. Is that fine? or should we code it in a way where we still see that there were readonly databases skipped? (due to how Pester v5 does skipping, I'm not sure how easy it'll be to get the database name in the skip output, but we would know something was skipped 🤔)

PS > Get-DbcConfig skip.backup.readonly

Name                 Value Description
----                 ----- -----------
skip.backup.readonly  True Check read-only databases for last backup

[github-actions]

Linux Test Results

    1 files  ±0    556 suites  ±0   25s ⏱️ -1s
1 940 tests ±0  1 940 ✅ ±0  0 💤 ±0  0 ❌ ±0 
2 318 runs  ±0  2 318 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 800879a. ± Comparison against base commit 948f90f.

♻️ This comment has been updated with latest results.

[github-actions]

WinPS51 Test Results

    1 files  ±0    556 suites  ±0   20s ⏱️ ±0s
1 940 tests ±0  1 940 ✅ ±0  0 💤 ±0  0 ❌ ±0 
2 318 runs  ±0  2 318 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 800879a. ± Comparison against base commit 948f90f.

♻️ This comment has been updated with latest results.

[github-actions]

WinPS71 Test Results

    1 files  ±0    556 suites  ±0   25s ⏱️ +2s
1 940 tests ±0  1 940 ✅ ±0  0 💤 ±0  0 ❌ ±0 
2 318 runs  ±0  2 318 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 800879a. ± Comparison against base commit 948f90f.

♻️ This comment has been updated with latest results.