Merge API rearchitecture changes into master

[dmitrii-ubskii]

What is the goal of this PR?

Merge the changes made to allow FFI compilation of Rust libraries via SWIG into the mainline branch of dependencies.

What are the changes implemented in this PR?

Update protobuf & gRPC dependencies (#442) Introduce Cargo project aspect, Cbindgen & SWIG rules (#447) Add maybe-async crate dependency (#449) Allow extra SWIG includes and extra args (#450) SWIG rules fixes (#456) Introduce SWIG Python rules (#460) Fix target label check in the cargo project generation (#462) Upgrade NodeJS dependencies: migrate to rules_js & rules_ts, upgrade gRPC & protobuf (#465) Allow linking SWIG Python for different platforms (#464) Allow linking SWIG Java for Windows (#467)

[typedb-bot]

PR Review Checklist

Do not edit the content of this comment. The PR reviewer should simply update this comment by ticking each review item below, as they get completed.

---

Trivial Change

• [x] This change is trivial and does not require a code or architecture review.

Code

• [ ] Packages, classes, and methods have a single domain of responsibility.
• [ ] Packages, classes, and methods are grouped into cohesive and consistent domain model.
• [ ] The code is canonical and the minimum required to achieve the goal.
• [ ] Modules, libraries, and APIs are easy to use, robust (foolproof and not errorprone), and tested.
• [ ] Logic and naming has clear narrative that communicates the accurate intent and responsibility of each module (e.g. method, class, etc.).
• [ ] The code is algorithmically efficient and scalable for the whole application.

Architecture

• [ ] Any required refactoring is completed, and the architecture does not introduce technical debt incidentally.
• [ ] Any required build and release automations are updated and/or implemented.
• [ ] Any new components follows a consistent style with respect to the pre-existing codebase.
• [ ] The architecture intuitively reflects the application domain, and is easy to understand.
• [ ] The architecture has a well-defined hierarchy of encapsulated components.
• [ ] The architecture is extensible and scalable.