Project cleanup, Manual build and upload

[jakub-kocka]

• Cleanuped the project repository
• Added manual build and upload for specified platforms, architectures and wheel(s)

1. All platforms and architectures workflow
2. Specified platforms and architectures worflow

• README.md was updated to explain how to use build-wheels-defined.yml (manual wheel(s) build and upload)

• Also os_dependencies directory was explained in README.md

• Upload workflow moved to reusable workflow - succeful run

Related

• Closes Ideas for future project improvements (IDF-8066)  #13

[github-actions]

	Messages
📖	You might consider squashing your 3 commits (simplifying branch history).
📖	This PR seems to be quite large (total lines of code: 1366), you might consider splitting it into smaller PRs

👋 Hello jakub-kocka, 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.
- 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.

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 802a865

[tomassebestik]

LGTM, thank you @jakub-kocka

[fhrbata]

LGTM, thank you

[jakub-kocka]

@dobairoland, Can you please take a look? If everything is OK, MR is ready to merge.