Fix aspect_bazel_lib dependency, update typedb and nodejs dependencies

[farost]

Usage and product changes

1. We update typedb dependencies to 2.28.3 before the release to verify that the builds are still correct before the driver release.
2. We update other dependencies that have previously broken the build because of the updated ts (nodejs) rules: dependencies ref with nodejs and csharp rules becoming more mature based on aspect_bazel_lib version globalization; typedb-protocol ref to propagate the fixed ts rules and fix its build based on this propagation.

Implementation

We use the updated rules fixed in dependencies and also update the code based on the new requirements of the updates ts rules. More details in the comments.

[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.