bump(websocket): 1.2.1 -> 1.2.2

[gabsuren]

1.2.2
Bug Fixes

• continuation after FIN in websocket client (websocket client decided to send first a FIN then a continuation, which is not allowed?! (IDFGH-11736) #460) (774d1c7)
• Re-applied refs to common comps idf_component.yml (9fe44a4)

[david-cermak]

I've checked the original PR and added few comments: #368

I'd suggest looking at and addressing these three issues:

1. esp_websocket_client_send_text() API might not include FIN flag
2. esp_websocket_client_send_bin() API might send message without the mandatory FIN flag.
3. Updateesp_websocket_client_send_with_exact_opcode() to include one additional parameter indicating whether or not to add the FIN flag in the last fragment.
4. These APIs do not lock the client not check parameters:

• esp_websocket_client_send_text_partial()
• esp_websocket_client_send_cont_msg()
• esp_websocket_client_send_bin_partial()
• esp_websocket_client_send_fin()

5. Check and fix the behaviour under CONFIG_ESP_WS_CLIENT_ENABLE_DYNAMIC_BUFFER=y

Testing

1. single API:

• esp_websocket_client_send_text() or bin version with size <= ws_client buffer size and check in wireshark for correct headers.
• same but with size > ws_client buffer and carefully check for ws message headers

2. multi message API:

• fist check with size <= ws_client buffer
• then check with size > ws_client buffer

• Test the same thing with CONFIG_ESP_WS_CLIENT_ENABLE_DYNAMIC_BUFFER

[david-cermak]

Let's go ahead and create a new release, but please fix the issue later