Adds RMT End of Transmission Level API

[SuGlider]

Description of Change

This PR adds a new API to RMT that allows the application to set the End of Transmission Level used at the end of writing to a RMT chanel. This level shall be set before transmiting and it can be changed between transmissions using the same pin.

Tests scenarios

ESP32 was tested using this Example:

#define BLINK_GPIO 2

// RMT is at 400KHz with a 2.5us tick
// This RMT data sends a 0.5Hz pulse with 1s High and 1s Low signal
rmt_data_t blink_1s_rmt_data[] = {
  // 400,000 x 2.5us = 1 second ON
  {25000, 1, 25000, 1,},
  {25000, 1, 25000, 1,},
  {25000, 1, 25000, 1,},
  {25000, 1, 25000, 1,},
  {25000, 1, 25000, 1,},
  {25000, 1, 25000, 1,},
  {25000, 1, 25000, 1,},
  {25000, 1, 25000, 1,},
  // 400,000 x 2.5us = 1 second OFF
  {25000, 0, 25000, 0,},
  {25000, 0, 25000, 0,},
  {25000, 0, 25000, 0,},
  {25000, 0, 25000, 0,},
  {25000, 0, 25000, 0,},
  {25000, 0, 25000, 0,},
  {25000, 0, 25000, 0,},
  {25000, 0, 25000, 0,},
  // Looping mode needs a Zero ending data to mark the EOF
  {0, 0, 0, 0}
};

void setup() {
  Serial.begin(115200);
  Serial.println("Starting Blink testing...");
  Serial.flush();
  
  // 1 RMT Block has 64 RMT_SYMBOLS (ESP32|ESP32S2) or 48 RMT_SYMBOLS (ESP32C3|ESP32S3)
  if (!rmtInit(BLINK_GPIO, RMT_TX_MODE, RMT_MEM_NUM_BLOCKS_1, 400000)) { //2.5us tick
    Serial.println("===> rmtInit Error!");
  }
  delay(1000); // initial state of the LED is LOW by default.
  
  // sets the End of Transmission Level to HIGH, after writing to the pin. DEFAULT is LOW.
  rmtSetEOT(BLINK_GPIO, HIGH);
    
  // Send the data and wait until it is done - set EOT level to HIGH
  if (!rmtWrite(BLINK_GPIO, blink_1s_rmt_data, RMT_SYMBOLS_OF(blink_1s_rmt_data) - 2, RMT_WAIT_FOR_EVER)) {
    Serial.println("===> rmtWrite Blink 1s Error!");
  }
    
  // LED shall stay 1 seconds OFF (initial state), BLINK: 1 second ON, 1 second OFF and then stay in HIGH level at the end.
}

void loop(){}

Related links

Closes #9235

[github-actions]

	Warnings
⚠️	Some issues found for the commit messages in this PR: the commit message "FIX (rmt): fixes eot_level setting using flags in the TX structure": summary looks empty type/action looks empty the commit message "RMT (feat): adds new feature to set the EOT level after writing RMT channel": summary looks empty type/action looks empty the commit message "RMT (featt): adds a new function to set EOT level after RMT writing": summary looks empty type/action looks empty the commit message "RMT(feat): Create RMT_EndOfTransmissionState.ino example": type/action should start with a lowercase letter type/action should be one of [change, ci, docs, feat, fix, refactor, remove, revert, test] the commit message "Update cores/esp32/esp32-hal-rmt.c": summary looks empty type/action looks empty the commit message "Update cores/esp32/esp32-hal-rmt.c": summary looks empty type/action looks empty the commit message "Update cores/esp32/esp32-hal-rmt.h": summary looks empty type/action looks empty the commit message "adds bool return to rmtSetEOT()": summary looks empty type/action looks empty the commit message "adds return value to rmtSetEOT()": summary looks empty type/action looks empty the commit message "adds return value to the rmtSetEOT() function": 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 10 commits (simplifying branch history).
⚠️	The source branch "RMT_EOT" 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 5181fea

[SuGlider]

@me-no-dev - All done. I tested it using the example from this PR and it works fine.

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

@SuGlider Just small typos in comments.
Tested with S2 and works perfectly :)