Multiple addresses input for TypeDB Cluster connections

[jamesreprise]

What is the goal of this PR?

We have implemented the ability to input multiple addresses for users connecting to TypeDB Cluster via Studio. End users will have a more seamless experience of connecting to Cluster using Studio as we have reduced the confusion surrounding how many addresses are necessary. It used to be the case that you could only provide a single address to the Cluster input dialog.

What are the changes implemented in this PR?

We have implemented the additional functionality primarily into the ServerDialog:

• A cluster addresses manager button.
• A manage addresses dialog that allows a user to add as many addresses as they please (but informs them that only 2-3 are likely to be necessary).
• On connecting to a cluster address, we pass the set of addresses rather than just one.

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

---

Code

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

Architecture

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

[alexjpwalker]

Somehow, the addresses placeholder doesn't look very faded, and as such it looks like it's possible to type into the field (but in fact, is not possible)