Updated esp_secure_cert_mgr and IDF v5.0 support

[dhavalgujar]

No description provided.

[puneet-arora15]

@dhavalgujar The documentation needs a bit of updating, as I'm going through the PR testing the process-
Getting started guide.md
2.3-1- python managed_components/espressif__esp_secure_cert_mgr/tools/configure_esp_secure_cert.py -p /* Serial port */ --keep_ds_data_on_host --efuse_key_id 1 --ca-cert cacert.pem --device-cert client.crt --private-key client.key --target_chip /* target chip */ --secure_cert_type cust_flash

2.3 -2 (Not required anymore as the python script writes to the partition)

I will keep adding comments for the doc stuff on here as I find them out

[kstribrnAmzn]

How was this tested?

[idea--list]

Am testing this PR for some days now. The last commit that i can get working on my ESP32S3 is that from 3rd january.
Later commits changed something about how certificate related things are implemented and whenever the FW tries to establish a TLS connection i always get esp-tls-mbedtls: mbedtls_x509_crt_parse returned -0x2180 message on the console. Meaning my certificates are not properly formatted. However i use the same certificates as before. Maybe i just miss something with the later commits to get them working.

While testing the commit from 3rd january when sub_pub_unsub_demo is enabled i often get this message in about 10-30 minutes after starting: Error or timed out waiting for ack for publish message X. Re-attempting publish. Right after that message it manages to reestablish the TLS connection, publishes the next message, but then sub_pub_unsub_demo stops doing anything, while ota_demo continues to run. That message comes from line 543 in sub_pub_unsub_demo.c. Inside prvPublishToTopic() there is a do-while loop. By commenting out the do and while part it hangs less often and the messages still get published as the prvPublishToTopic() function is called anyways regularly by prvSubscribePublishUnsubscribeTask. So not sure if the do while loop is of any benefit there.

Update: i added some heap and stack statistics to the code. Tasks SubPub0 and OTADemoTask had only 276 and 796 bytes of free stack which is way too low. So increased the stack size of those including coreMQTTAgentConnectionTask to 4096. SubPub0 still stops within an hour. Next i pinned all the tasks to core 0, which did not help. Then i also have set all the task priorities to the same and let it run overnight. After applying all these changes the program ran 9087 seconds without SubPub0 stopping. Instead of that all the tasks stopped, the system does not do anything for hours now and the power consumption has doubled. Despite more than 130 KB is free on heap and all stacks have more than 1400 bytes free. Have no idea why this happens.

[JasonYan324]

@dhavalgujar The documentation needs a bit of updating, as I'm going through the PR testing the process- Getting started guide.md 2.3-1- python managed_components/espressif__esp_secure_cert_mgr/tools/configure_esp_secure_cert.py -p /* Serial port */ --keep_ds_data_on_host --efuse_key_id 1 --ca-cert cacert.pem --device-cert client.crt --private-key client.key --target_chip /* target chip */ --secure_cert_type cust_flash

2.3 -2 (Not required anymore as the python script writes to the partition)

I will keep adding comments for the doc stuff on here as I find them out

IDF5.2.2 & IDF5.3 are not support yet