STM32 USB connect procedure update

[jeromecoutant]

Summary of changes

USB tests restarted during #13406

Tested with:

• STM32F1: Need external Pull up on USB DP
• STM32WB: Non regression OK, Internal pull up on DP pin OK
• STM32L4: Non regression OK

@Allmoz
@maciejbocianski

Impact of changes

Migration actions required

Documentation

---

Pull request type

[x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

---

Test results

[] No Tests required for this change (E.g docs only update)
[x] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

---

Reviewers

---

[ciarmcom]

@jeromecoutant, thank you for your changes.
@ARMmbed/mbed-os-maintainers please review.

[maciejbocianski]

@jeromecoutant what actually it changes to wb55? It's worth backporting ?

[0xc0170]

CI started

[mbed-ci]

Jenkins CI Test : ✔️ SUCCESS

Build Number: 1 | 🔒 Jenkins CI Job | 🌐 Logs & Artifacts

CLICK for Detailed Summary

jobs	Status
jenkins-ci/mbed-os-ci_unittests	✔️
jenkins-ci/mbed-os-ci_build-ARM	✔️
jenkins-ci/mbed-os-ci_build-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_cloud-client-pytest	✔️
jenkins-ci/mbed-os-ci_dynamic-memory-usage	✔️
jenkins-ci/mbed-os-ci_greentea-test	✔️

[jeromecoutant]

what actually it changes to wb55? It's worth backporting ?

I agree this should not impact STM32WB.
This align code and USB behavior between STM32 families.