Bump NATS.Net from 2.2.3 to 2.3.0

[dependabot]

Bumps NATS.Net from 2.2.3 to 2.3.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

###### Microsoft Reviewers: [Open in CodeFlow](https://microsoft.github.io/open-pr/?codeflow=https://github.com//pull/4808)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

[danmoseley]

@radical tests timed out on Linux. Is there any way to tell what tests? I downloaded the test logs, and they seem to be only for successful test jobs. Ideally we'd see literally the name of the test that took the most time -- presumably the last one as it hung.

[radical]

@radical tests timed out on Linux. Is there any way to tell what tests? I downloaded the test logs, and they seem to be only for successful test jobs. Ideally we'd see literally the name of the test that took the most time -- presumably the last one as it hung.

None of the tests failed that's why the test reports don't show failures. The Run Helix tests step timed out as it was downloading other results files. And this was because all the tests waited for ~72mins for helix agents to become available. All the tests ran in 0-12mins after that. From kusto:

So, the timeout was due to helix being very busy. I will trigger a re-run.

[danmoseley]

Ah, thanks. Should we increase timeouts again to accommodate Helix delays? Or would that be worse situation, as we'd be waiting longer for a result when a test genuinely hangs?