ClientWebSocketResponse.close_code will be None when there are concurrent async task receiving data and closing connection

[wenleix]

Describe the bug

If one asyncio task is waiting on receiving data and another asyncio task is closing the connection. The ClientWebSocketResponse.close_code will be None after connection closed.

It looks like the following is happening:

1. close() called and feed WS_CLOSING_MESSAGE:

   aiohttp/aiohttp/client_ws.py

   Lines 191 to 193 in fde452d

   	if self._waiting is not None and not self._closed:
   	self._reader.feed_data(WS_CLOSING_MESSAGE, 0)
   	await self._waiting

2. receive() received WS_CLOSING_MESSAGE , mark self._closing to be True:

   aiohttp/aiohttp/client_ws.py

   Lines 285 to 286 in fde452d

   	elif msg.type == WSMsgType.CLOSING:
   	self._closing = True

3. close() (after sent out the close message to server) find self._closing is True, close the response and return, WITHOUT setting self._close_code:

   aiohttp/aiohttp/client_ws.py

   Lines 210 to 212 in fde452d

   	if self._closing:
   	self._response.close()
   	return True

To Reproduce

See the steps in https://github.com/wenleix/aiohttp_recv_upon_close

Expected behavior

Expect to have closed code 1000, i.e.

Waiting for message
Closed code: 1000

Logs/tracebacks

The actual result is :

Waiting for message
Closed code: None

### Python Version

```console
$ python --version

Python 3.9.13

### aiohttp Version

```console
$ python -m pip show aiohttp

Name: aiohttp
Version: 3.8.4
Summary: Async http client/server framework (asyncio)
Home-page: https://github.com/aio-libs/aiohttp
Author:
Author-email:
License: Apache 2
Requires: aiosignal, async-timeout, attrs, charset-normalizer, frozenlist, multidict, yarl
Required-by:

### multidict Version

```console
$ python -m pip show multidict

Name: multidict
Version: 6.0.4
Summary: multidict implementation
Home-page: https://github.com/aio-libs/multidict
Author: Andrew Svetlov
Author-email: andrew.svetlov@gmail.com
License: Apache 2
Requires:
Required-by: aiohttp, yarl

### yarl Version

```console
$ python -m pip show yarl

Name: yarl
Version: 1.9.2
Summary: Yet another URL library
Home-page: https://github.com/aio-libs/yarl/
Author: Andrew Svetlov
Author-email: andrew.svetlov@gmail.com
License: Apache-2.0
Requires: idna, multidict
Required-by: aiohttp

### OS

macOS

### Related component

Client

### Additional context

_No response_

### Code of Conduct

- [X] I agree to follow the aio-libs Code of Conduct

[Dreamsorcerer]

Looks to me like this should be changed:

- if self._waiting is not None and not self._closed:
+ if self._waiting is not None and not self._closing:
+     self._closing = True

Otherwise, multiple close() calls could send multiple CLOSING messages.

Then:

- if self._closing:
+ if self._close_code:

So, in error cases, where the code is already set, it closes immediately. In normal closing, it would continue to the end of the closing logic.