The one where...

Finally release ISHRemote v1.0, honestly nothing changed regarding quality. Some people find v1.0 more pleasing though :)
Main reason for v1.0 is to prepare the trunk branch of source control for .NET (Core) as described in the ThePlan-ISHRemote-7.0.md

Breaking changes

Windows PowerShell older than 5.1 is no longer supported. In turn also .NET Framework 4.8, the final Windows .NET Framework version by Microsoft is also required. This enables TLS 1.3 support in turn. #102
Stop Strong Naming the ISHRemote assembly #80 Thanks @ddemeyer

Add-IshBackgroundTask fix regarding date time parsing incoming dates incorrectly swapping month/day #137 Thanks @ddemeyer
New-IshObfuscatedFile, New-IshDitaGeneralizedXml and Test-IshValidXml received updated xml catalog handling classes aligning with product 14SP4/14.0.4 code base. #146 Thanks @jlaridon

Enabled Github Actions Continuous Integration, see .\.github\workflows\continuous-integration.yml #102 Thanks @ivandelagemaat
Made several tests environment agnostic by adding some explicit default entries in ISHRemote.PesterSetup.ps1, but in turn allow overrides in later loaded ISHRemote.PesterSetup.Debug.ps1 by re-initializing variables like
```
$ishLngLabel = 'en-us'
$ishLngTarget1 = 'VLANGUAGEESES'
$ishLngTarget1Label = 'es-es'
$ishLngTarget2 = 'VLANGUAGEDEDE'
$ishLngTarget2Label = 'de-de'
$ishLngCombination = 'en-us'
```
Added more Pester Tests, current results below where:
- the skipped are about SslPolicyErrors testing
- the failed are about IMetadata bound fields (issue #58)
- Invoke-Pester 5.3.0 results on the same machine are
```
Tests completed in 902.47s
Tests Passed: 914, Failed: 0, Skipped: 9 NotRun: 0
```