fix(ci): Fix tests and workflows

[lucasssvaz]

Description of Change

This pull request introduces support for passing Wi-Fi credentials dynamically to hardware tests, improving flexibility and enabling tests to run in different Wi-Fi environments. The changes include updates to test scripts, workflow files, and test code to accept and process Wi-Fi SSID and password as arguments, rather than hardcoding them.

Wi-Fi credential handling improvements:

• .github/scripts/tests_run.sh: Added support for -wifi-ssid and -wifi-password command-line arguments, which are passed to pytest and included in test retries. [1] [2] [3]
• tests/conftest.py: Introduced pytest options and session-scoped fixtures to provide wifi_ssid and wifi_pass values to tests.
• tests/validation/wifi/test_wifi.py: Updated the test to use the new fixtures, send credentials to the device, and verify they are received correctly. The test now fails if no SSID is provided.
• tests/validation/wifi/wifi.ino: Modified the firmware to read Wi-Fi credentials from serial input at runtime, instead of using hardcoded values. [1] [2] [3]

Workflow and CI integration:

• .github/workflows/tests_hw_wokwi.yml, .gitlab/workflows/hw_test_template.yml: Updated workflows to pass Wi-Fi credentials as environment variables and script arguments to the test runner, ensuring tests run with the correct network settings. [1] [2]

Other improvements:

• tests/pytest.ini: Added configuration to suppress experimental warnings and set the JUnit report family.
• .github/workflows/release.yml: Changed hosted binary copy command to use a more explicit update mode.
• tests/performance/ramspeed/ramspeed.ino: Improved memory allocation by using specific heap capabilities.
• .github/workflows/tests_hw_wokwi.yml: Reformatted the variables block for readability.

Test Scenarios

Tested locally

[github-actions]

	Messages
📖	🎉 Good Job! All checks are passing!

👋 Hello lucasssvaz, we appreciate your contribution to this project!

---

📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

---

🖊️ Please also make sure you have read and signed the Contributor License Agreement for 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.
- 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 35cae5e

[github-actions]

Test Results

152 files  152 suites   1h 0m 52s ⏱️
 53 tests  36 ✅ 0 💤  9 ❌  8 🔥
392 runs  335 ✅ 0 💤 21 ❌ 36 🔥

For more details on these failures and errors, see this check.

Results for commit 8669f1c.

♻️ This comment has been updated with latest results.

[me-no-dev]

@P-R-O-C-H-Y PTAL