Bump aiohttp and requests to more secure versions

[prijendev]

Description of change

• Bump requests from 2.31.0 to 3.32.3

• Bump aiohttp from 3.8.5 to 3.11.9

• In aiohttp version 3.8.5, the get_event_loop method was used to retrieve the current event loop. This method would return the running event loop if one existed; otherwise, it would return the default event loop. However, in the latest versions of aiohttp, the get_running_loop method is used instead. Unlike get_event_loop, get_running_loop raises an error if no event loop is currently running.

• In our case, we create an event loop and set it as the current loop for the thread. However, since the loop is not yet in a running state, the latest aiohttp version throws an error when it tries to find a running event loop.

  File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.8/threading.py", line 870, in run
    self._target(*self._args, **self._kwargs)
  File "/opt/code/target-stitch/target_stitch/__init__.py", line 73, in start_loop
    OUR_SESSION = aiohttp.ClientSession(connector=aiohttp.TCPConnector(), timeout=timeout)
  File "/usr/local/share/virtualenvs/target-stitch/lib/python3.8/site-packages/aiohttp/connector.py", line 851, in __init__
    super().__init__(
  File "/usr/local/share/virtualenvs/target-stitch/lib/python3.8/site-packages/aiohttp/connector.py", line 258, in __init__
    loop = loop or asyncio.get_running_loop()
RuntimeError: no running event loop

• To resolve this, we explicitly pass our created event loop to the TCPConnector object. By doing so, aiohttp directly uses the provided event loop without attempting to locate a running loop, avoiding the error.

QA steps

• automated tests passing
• Verified that the target emits records as expected by running tap with the orchestrator.
• Verified the logs target logs with the current version and previous version.
• Verified that the target does not break in between while processing the tap records.

Risks

Rollback steps

• revert this branch

AI generated code

https://internal.qlik.dev/general/ways-of-working/code-reviews/#guidelines-for-ai-generated-code

• this PR has been written with the help of GitHub Copilot or another generative AI tool