fix(tests): Address a port conflict issue in the non-blocking logger test

[arya2]

Motivation

The non_blocking_logger() test was missed when disabling tests that could cause port conflicts in #8551 and when addressing port conflict issues in #8624 to close #8553.

We want to avoid port conflicts in this test too.

Solution

Uses an OS-assigned port in the non_blocking_logger() test's Zebrad child process's RPC listen address, and read the listen address from Zebra's logs

Follow-up Work

Try addressing port conflicts in tests related to Zebra's tracing filter and prometheus metrics endpoints as well. Search for uses of random_known_port() and limit its usage to the local_listener_fixed_port_localhost_addr_v4() and local_listener_fixed_port_localhost_addr_v6() tests.

PR Author's Checklist

• The PR name will make sense to users.
• The PR provides a CHANGELOG summary.
• The solution is tested.
• The documentation is up to date.
• The PR has a priority label.

PR Reviewer's Checklist

• The PR Author's checklist is complete.
• The PR resolves the issue.

[mpguerra]

@Mergifyio refresh

[mergify]

refresh

✅ Pull request refreshed