Add Bluetooth Common Data Types definitions (IDFGH-16960)

[acouvreur]

Is your feature request related to a problem?

All BLE examples that are defining raw advertisement data are using the Data Type Specification in raw hexadecimal form:

esp-idf/examples/bluetooth/bluedroid/ble_50/ble50_throughput/throughput_server/main/example_ble_server_throughput.c

Lines 100 to 107 in fcae328

	static uint8_t ext_adv_raw_data[] = {
	0x02, 0x01, 0x06,
	0x02, 0x0a, 0xeb,
	0x03, 0x03, 0xab, 0xcd,
	0x11, 0x07, 0xfb, 0x34, 0x9b, 0x5f, 0x80, 0x00, 0x00, 0x80, 0x00, 0x10, 0x00, 0x00, 0xEE, 0x00, 0x00, 0x00,
	0x11, 0x07, 0xfb, 0x34, 0x9b, 0x5f, 0x80, 0x00, 0x00, 0x80, 0x00, 0x10, 0x00, 0x00, 0xFF, 0x00, 0x00, 0x00,
	0x14, 0X09, 'T', 'H', 'R', 'O', 'U', 'G', 'H', 'P', 'U', 'T', '_', 'P', 'H', 'Y', '_', 'D', 'E', 'M', 'O',
	};

The data specification let you send data in the following format:

The list of available flags is available in the bluetooth specification at 2.3 Common Data Types: https://www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/Assigned_Numbers/out/en/Assigned_Numbers.pdf

Describe the solution you'd like.

The bluetooth common header file should include a definition of each of those flags. Then, each example should switch to using this definition for better clarity.

Describe alternatives you've considered.

Create my own header file, but I think it has a lot of value and would benefit the community.

Additional context.

I can create a pull request for this.

[acouvreur]

It's worth noting that this list is already implemented in the ble_conn_manager component as a private include:

https://github.com/espressif/esp-iot-solution/blob/b2cd32d27d442641ec63d2a854639a49508e2428/components/bluetooth/ble_conn_mgr/src/priv_includes/esp_nimble.h#L25-L46