Make the libtorrent tests more responsive

[drew2a]

This PR doesn't completely solve the issue causing the flakiness of the libtorrent tests. However, the changes have made the tests more responsive and should, at the very least, prevent the main thread from freezing.

Besides minor refactoring, there are two significant changes in this PR:

1. An asyncio switch was added to the wait_for_status function due to the potential of blocking the main thread during pytest execution. To understand the possibility, consider this example:

   tribler/src/tribler/core/utilities/tests/test_async_force_switch.py

   Lines 10 to 34 in 018cd5f

   	async def test_without_switch():
   	# In this test, we reproduce the asyncio behavior where there's a possibility
   	# to block the main thread if there's no blocking event in the coroutine.
   	class EndOfTheTest(TimeoutError):
   	"""Exception to stop a test after 0.2 seconds."""
   	start_time = time.time()
   	async def any_non_blocking_coro():
   	duration = time.time() - start_time
   	if duration >= 0.2:
   	# to prevent indefinite block of a thread, raise an exception after 2 seconds.
   	raise EndOfTheTest
   	# With this line ↓
   	# await asyncio.sleep(0)
   	# `asyncio.wait_for()` will work as expected, interrupting the execution of the coroutine after 0.1 sec.
   	# Without this line, the main thread will be blocked indefinitely.
   	async def a():
   	while True:
   	await any_non_blocking_coro()
   	# We are waiting for the timeout, but coroutine a() will never be cancelled.
   	with pytest.raises(EndOfTheTest):
   	await asyncio.wait_for(a(), timeout=0.1)

2. The shutdown logic has been rewritten to be slightly more accurate. While this change may not directly influence test stability, it could contribute slightly to it.

Related to #7495

Refs:

• https://docs.python.org/3/library/asyncio-task.html#asyncio.Task.cancel
• https://textual.textualize.io/blog/2023/02/11/the-heisenbug-lurking-in-your-async-code/