Fix Flaky Test in AWS X-Ray Remote Sampler Client Test

[jj22ee]

Issue #, if available:
(Recreated PR to trigger Analyzer Checks)

This PR fixes flaky test test_urls_excluded_from_sampling, causing issues in PR workflows

• Example: https://github.com/aws-observability/aws-otel-python-instrumentation/actions/runs/9103811387/job/25026448867

Instantiation of AwsXRayRemoteSampler will spawn processes that will regularly (every 10s and 300s) make a Request call, and these processes stay alive between different unit tests. This means that the test that counts the number instrumented Request calls is affected by these "orphaned" processes.

The solution is to stop these processes inside the tests that they are created from, or stop them from being spawned in the first place if they are not needed.

Description of changes:

• Stop the daemon rule and target poller processes inside the tests that they are created from, or stop them from being spawned in the first place if they are not needed.
• Revert previous fix attempt
• Add test for version to increase and pass code coverage

Testing:

• Reproduced failing test by running test in loop of 10000 runs
• Failing test not reproducible after applying fix.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.