Apply Toit patches onto 5.3.1

[floitsch]

No description provided.

[github-actions]

	Warnings
⚠️	Some issues found for the commit messages in this PR: the commit message "Add Cmpctmalloc (#78)": summary looks empty type/action looks empty the commit message "Add README.toitlang": summary looks empty type/action looks empty the commit message "Added padding to DROM section to allow for drom rewrites": summary looks empty type/action looks empty body must have leading blank line the commit message "Change origin of mbedtls submodule to Toit fork (#80)": summary looks empty type/action looks empty the commit message "Fix aligned allocations and disallow offset-allocations.": summary should not end with a period (full stop) summary looks empty type/action looks empty the commit message "Remove 'static' on start_cpu0_default. (#81)": summary looks empty type/action looks empty the commit message "Roll mbedtls.": summary should not end with a period (full stop) summary looks empty type/action looks empty the commit message "cmpctmalloc: Protect MIN and MAX macros. (#82)": probably contains Jira ticket reference (1-11). Please remove Jira tickets from commit messages. body's lines must not be longer than 100 characters type/action should be one of [change, ci, docs, feat, fix, refactor, remove, revert, test] 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 9 commits (simplifying branch history).
⚠️	The Pull Request description is empty. Please provide a detailed description.
⚠️	The **target branch** for this Pull Request **must be the default branch** of the project (`master`). If you would like to add this feature to a different branch, please state this in the PR description and we will consider it.

	Messages
📖	This PR seems to be quite large (total lines of code: 2551), you might consider splitting it into smaller PRs

👋 Hello floitsch, 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.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- Addressing info messages (📖) is strongly recommended; they're less critical but valuable.
- 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 via this public GitHub repository.

This GitHub project is public mirror of our internal git repository

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 synchronize it into our internal git repository.
4. In the internal git repository 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.
5. If the change is approved and passes the tests it is merged into the default branch.
5. On next sync from the internal git repository merged change will appear in this public GitHub repository.

Generated by 🚫 dangerJS against e60edc2

[kasperl]

Still looks good!