Feature/net5

[rkm]

Proposed Changes

Upgrade all projects to net5, and fixup corresponding CI configs.

Types of changes

What types of changes does your code introduce? Tick all that apply.

• Bugfix (non-breaking change which fixes an issue)
• New Feature (non-breaking change which adds functionality)
• Breaking Change (fix or feature that would cause existing functionality to not work as expected)
• Documentation-Only Update (if none of the other choices apply)
  • In this case, ensure that the message of the head commit from the source branch is prefixed with [skip ci]

Checklist

By opening this PR, I confirm that I have:

• Reviewed the contributing guidelines for this repository
• Ensured that the PR branch is in sync with the target branch (i.e. it is automatically merge-able)
• Updated any relevant API documentation
• Created or updated any tests if relevant
• Created a news file
  • NOTE: This must include any changes to any of the following files: default.yaml, any of the RabbitMQ server configurations, GlobalOptions.cs
• Listed myself in the CONTRIBUTORS file 🚀
• Requested a review by one of the repository maintainers

Issues

• Closes Upgrade to .NET 5 #707

[lgtm-com]

This pull request introduces 3 alerts and fixes 2 when merging c7d7d95 into c618b22 - view on LGTM.com

new alerts:

• 3 for Missing Dispose call on local IDisposable

fixed alerts:

• 2 for Dereferenced variable may be null

[rkm]

Let's tackle those new(?) LGTM issues as a separate PR

[lgtm-com]

This pull request introduces 3 alerts and fixes 2 when merging a0105b2 into c618b22 - view on LGTM.com

new alerts:

• 3 for Missing Dispose call on local IDisposable

fixed alerts:

• 2 for Dereferenced variable may be null

[lgtm-com]

This pull request fixes 2 alerts when merging 58883ed into c618b22 - view on LGTM.com

fixed alerts:

• 2 for Dereferenced variable may be null