Update embassy-sync and embassy-executor

[bramsdell-ms]

Updating versions for embassy-sync and embassy-executor. Dependent on OpenDevicePartnership/tps6699x#89

[github-actions]

Cargo Vet Audit Failed

cargo vet has failed in this PR. Please run cargo vet --locked locally to check for new or updated unvetted dependencies.
Details about the vetting process can be found in supply-chain/README.md

If the unvetted dependencies are not needed

Please modify Cargo.toml file to avoid including the dependencies.

If the unvetted dependencies are needed

Post a new comment with the questionnaire below to the PR to help the auditors vet the dependencies.
After the auditors have vetted the dependencies, the PR will need to be rebased to pick up the new audits and pass this check.

Copy and paste the questionnaire as a new comment and provide your answers:

1. What crates (with version) need to be audited?

2. How many of the crates are version updates vs new dependencies?

3. To confirm none of the already included crates serve your needs, please provide a brief description of the purpose of the new crates.

4. Any extra notes to the auditors to help with their audits.

[bramsdell-ms]

This can be undone when the OpenDevicePartnership/tps6699x#89 lands

[kurtjd]

As mentioned on OpenDevicePartnership/tps6699x#89, these versions have not been published to crates.io yet so we can't merge this until that is the case.

[bramsdell-ms]

Which repos are acceptable to refer to by git vs. need to be in crates.io? One option might be to change to a git reference.

[kurtjd]

Which repos are acceptable to refer to by git vs. need to be in crates.io? One option might be to change to a git reference.

I believe we are trying to stick to crates.io releases only for Embassy. Recently we migrated away from git deps to crates.io for Embassy: #479

@jerrysxie does this match your understanding as well?

[jerrysxie]

Which repos are acceptable to refer to by git vs. need to be in crates.io? One option might be to change to a git reference.

I believe we are trying to stick to crates.io releases only for Embassy. Recently we migrated away from git deps to crates.io for Embassy: #479

@jerrysxie does this match your understanding as well?

@kurtjd @bramsdell-ms We switched to crate.io version to be more stable for our clients due to some subtle dependency between the embassy crates. There is no set in stone rule regarding crate.io or git dependency. We just have to be consistent throughout the entire ODP stack to not cause embassy dependency conflict to cause subtle breakages.

For this change, it will be a problem for us since embassy-imxrt is not updated, so if this merged, client downstream depending on embedded-services and embassy-imxrt might have issue as there will be 2 different versions of embassy-sync in the dependency tree.