Fixes HW Serial attaching pins, PHY initialization, crash after end()

[SuGlider]

Description of Change

Fixes:

• pin number error
• PHY initialization that prevented HW Serial to start correctly and get enumerated after end() or detaching pins
• crash after executing end()
• force USB Host enumeration in order to set the right state to detect first time sending data to the HOST (CDC Connection)

Tests scenarios

Tested with ESP32-C3, ESP32-S3, ESP32-C6, ESP32-H2

// HW Serial CDC mode with CDC on boot enabled

void setup() {
  Serial.begin();
  Serial.end();
  Serial.begin();
  // waits until Serial Monitor is open
  while (!Serial) delay(100);
  Serial.println();
  Serial.println("Started!");
  Serial.println("");
}

void loop() {
  Serial.println("loop...");
  delay(1000);
}

Related links

Fixes #9360

[github-actions]

	Warnings
⚠️	Some issues found for the commit messages in this PR: the commit message "fix git stash/commit added lines": summary looks empty type/action looks empty the commit message "fix: HWCDC pin number": summary looks too short the commit message "fix: PHY initialization": body's lines must not be longer than 100 characters summary looks too short the commit message "fix: crashing end()": body's lines must not be longer than 100 characters summary looks too short the commit message "fixes C6|H2 issue": summary looks empty type/action looks empty the commit message "fixes usb_phy_ll include and call": summary looks empty type/action looks empty the commit message "fixes": summary looks empty type/action looks empty the commit message "github commit problem": summary looks empty type/action looks empty the commit message "reduces number of debug messages": summary looks empty type/action looks empty the commit message "roll back": summary looks empty type/action looks empty the commit message "solves HWSerial initialization": summary looks empty type/action looks empty Please fix these commit messages - here are some basic tips: follow Conventional Commits style correct format of commit message should be: <type/action>(<scope/component>): <summary>, for example fix(esp32): Fixed startup timeout issue allowed types are: change,ci,docs,feat,fix,refactor,remove,revert,test sufficiently descriptive message summary should be between 20 to 72 characters and start with upper case letter avoid Jira references in commit messages (unavailable/irrelevant for our customers) TIP: Install pre-commit hooks and run this check when committing (uses the Conventional Precommit Linter).
⚠️	Please consider squashing your 11 commits (simplifying branch history).
⚠️	The source branch "HWCDC_pins" incorrect format: contains uppercase letters. This can cause troubles on case-insensitive file systems (macOS). Please rename your branch.

👋 Hello SuGlider, 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 e731329

[Jason2866]

The roll back re-introduces CI compile errors for the others CDC MCUs
Edit: since completely removed it is fine!

[SuGlider]

The roll back re-introduces CI compile errors for the others CDC MCUs Edit: since completely removed it is fine!

I decided to set the registers directly for all the SoC. It works fine now.

[P-R-O-C-H-Y]

LGTM! Tested with S3 and the issue is gone. Great job :)

[lucasssvaz]

Lgtm

[lbernstone]

Tested on C6 👍