lock working for async recv

[maxwellflitton]

async batching is now supported with the following unit test:

class TestAsyncWsSurrealConnection(IsolatedAsyncioTestCase):

    async def asyncSetUp(self):
        self.url = "ws://localhost:8000"
        self.password = "root"
        self.username = "root"
        self.vars_params = {
            "username": self.username,
            "password": self.password,
        }
        self.database_name = "test_db"
        self.namespace = "test_ns"
        self.data = {
            "username": self.username,
            "password": self.password,
        }
        self.connection = AsyncWsSurrealConnection(self.url)
        _ = await self.connection.signin(self.vars_params)
        _ = await self.connection.use(namespace=self.namespace, database=self.database_name)

    async def test_batch(self):
        async with asyncio.TaskGroup() as tg:
            tasks = [tg.create_task(self.connection.query("select $p**2 as ret from {}", dict(p=num))) for num in range(5)]

        outcome = [t.result()[0]["ret"] for t in tasks]
        self.assertEqual([0, 1, 4, 9, 16], outcome)
        await self.connection.socket.close()

[maxwellflitton]

@Anton-2 thanks for the pull request, your approach has been merged to this branch now. However, the tests are all now showing a lot of resource warnings flaky tests where some of the tests are randomly breaking. I'm going to open up another branch and just push the Lock so we get the functionality for now and then continue to work on this. Our CI runs the test suite single threaded multiple times with different python versions and different surrealDB versions. Some of these query are now randomly coming back with wrong length of results, or a certain record already being there. While your solution is more elegant and performant than a lock, we have to ensure stability first.

[maxwellflitton]

@Anton-2 done some jigging with the workflows and reset my system in terms of dependencies and you're code is now passing all tests with no warnings. So I'm going to merge your code into main, thanks for being patient and I really appreciate the pull request. Your commits are in this pull request so I haven't erased your contribution.