fix(no_std_executor): Ensure thread-safe initialization of Executor in current function

[younes-io]

fix(no_std_executor): Ensure thread-safe initialization of Executor in current function

• Introduced atomic operations to prevent concurrent initialization of Executor
• Utilized compare_exchange_weak for safe and single initialization
• Enhanced overall thread safety and memory safety in a no_std environment

Current behavior

Proposed changes

Checks

• [x] All commits in this Pull Request are signed and Verified by Github.
• [x] All commits in this Pull Request follow the Ockam commit message convention.
• [x] There are no Merge commits in this Pull Request. Ockam repo maintains a linear commit history. We merge Pull Requests by rebasing them onto the develop branch. Rebasing to the latest develop branch and force pushing to your Pull Request branch is okay.
• [x] I have read and accept the Ockam Community Code of Conduct.
• [x] I have read and accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam repository. The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a separate Pull Request, this will mark the commit as verified.

[younes-io]

Can someone help me fix the commit msg ?

[younes-io]

Closing because this keeps failing and I get a million emails a day... and I don't have access to the CI/CD