fix: Split provisioning into two parts for better synchronization

[kvp1703]

Description of Change

Split provisioning into two parts for better synchronization.
The user node association (cloud_user_assoc) endpoint failed to register in the provisioning workflow because provisioning began before the endpoint creation.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

	Warnings
⚠️	The **target branch** for this Pull Request **must be the default branch** of the project (`master`). If you would like to add this feature to a different branch, please state this in the PR description and we will consider it.

👋 Hello kvp1703, we appreciate your contribution to this project!

---

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 4ecfd35

[github-actions]

Test Results

 62 files   62 suites   5m 42s ⏱️
 21 tests  21 ✅ 0 💤 0 ❌
154 runs  154 ✅ 0 💤 0 ❌

Results for commit 4ecfd35.

♻️ This comment has been updated with latest results.

[github-actions]

Memory usage test (comparing PR against master branch)

The table below shows the summary of memory usage change (decrease - increase) in bytes and percentage for each target.

Memory	FLASH [bytes]		FLASH [%]		RAM [bytes]		RAM [%]
Target	DEC	INC	DEC	INC	DEC	INC	DEC	INC
ESP32S3	0	‼️ +20K	0.00	‼️ +1.08	0	‼️ +4K	0.00	‼️ +6.53
ESP32S2	💚 -14K	0	💚 -1.46	0.00	0	‼️ +3K	0.00	‼️ +7.35
ESP32C3	0	‼️ +35K	0.00	‼️ +1.79	0	⚠️ +2024	0.00	‼️ +3.66
ESP32C6	0	‼️ +49K	0.00	‼️ +2.39	0	‼️ +25K	0.00	‼️ +39.41
ESP32	0	‼️ +10K	0.00	⚠️ +0.51	0	⚠️ +1384	0.00	‼️ +2.41

Click to expand the detailed deltas report [usage change in BYTES]

Target	ESP32S3		ESP32S2		ESP32C3		ESP32C6		ESP32
Example	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM	FLASH	RAM
RainMaker/examples/RMakerSwitch	‼️ +20K	‼️ +3K	💚 -9K	⚠️ +1828	‼️ +35K	⚠️ +1880	‼️ +49K	‼️ +25K	‼️ +10K	⚠️ +480
WiFiProv/examples/WiFiProv	‼️ +15K	‼️ +4K	💚 -14K	‼️ +3K	‼️ +26K	⚠️ +2024	‼️ +41K	‼️ +3K	‼️ +6K	⚠️ +1384