Fix frequent setup-uv CI failures on windows and macos

[bmos]

What is this change?

• We keep having random intermittent test failures during the setup-uv action step. These failures are because windows and macos runners don't support eBPF. This means that during initialization our firewall is configured with IPs matching our whitelist but those IPs do not always match those that are contacted during setup-up (the github IPs rotate, so multiple DNS requests may get different results).
• As we are no longer blocking unexpected outbound traffic, we should be careful that our tests do not result in actual HTTP traffic.

Considerations for discussion

• We could conditionally use block on the ubuntu runners, which could help reveal tests that are making HTTP requests, but it might be confusing to have improperly-written tests failing with timeouts on ubuntu but not macos and windows.
• I didn't remove the whitelist, as this deficiency of harden-runner may be resolved at some point in the future.

How to test the changes (if needed)

• Observe that tests pass.

Breaking Changes

Breaking changes are changes to our public API which may require existing users to change their code. If there are no breaking changes, any existing parsons user should not need to do anything after updating their parsons version.

Does this PR introduce breaking changes?

• label: Breaking change — This PR introduces one or more breaking changes.
• label: Non-breaking change — This PR does not introduce one or more breaking changes.

Details (if needed)

• (List out any changes to the API that may cause breaks for developer implementation.)

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
parsons/utilities
api_connector.py
datetime.py
Project Total

This report was generated by python-coverage-comment-action