Dependencies and rules refactoring for the C# driver deployment

[farost]

What is the goal of this PR?

We prepare tools for the C# driver release, namely and clean all the old TODOs left from the initial PR.

What are the changes implemented in this PR?

Added:

• nuget deployment URLs for referencing from the C# bazel rules.

Updated:

• Refactored the bazel rule for native C# library generation. Cleaned TODOs.

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

[farost]

There is a series of connected PRs:

1. Bazel-distribution with fresh Bazel rules
2. Dependencies with updated refs and todo cleanings
3. TypeDB Driver with new Bazel rules usage, updated documentation, etc