Web: Provide accurate actionable steps with duplicate db name error

[kimlisa]

Part of discover work to improve rds flow:

• Before, we gave a user ambiguous "duplicate db name, use a different name and try again". Now we do some tests to provide a user more actionable steps to take depending on if a db server exists for the database or not
• We now pre-check if the rds db's we fetched from aws has already been enrolled and if enrolled, prevent user from re-enrolling by making table row disabled

Screenshot

note: the tctl command is actually tctl rm db/<dbname> i just took the screenshot before i caught it

Self-hosted, duplicate db with a database server:

Self-hosted, duplicated db (no db server)

aws rds, dup db (no db server)

aws rds, dup db with a db server

disable row:

[ryanclark]

Just a couple of minor comments

[ryanclark]

I think Boolean() here is redundant as you're using &&

[kimlisa]

i get this type error if i don't cast it:

Argument of type 'string' is not assignable to parameter of type 'boolean'

[gzdunek]

I will take a look on Monday.

[gzdunek]

Nit: I think that long error messages look better as sentences:

Failed to register database: a database with the name "${dbName}" is a part of this cluster, set 
"teleport.dev/database_name" tag on this RDS instance to use a different name and try again.

(but if other error messages are not written this way then let it stay as it is)

[kimlisa]

Nit: I think that long error messages look better as sentences:

Failed to register database: a database with the name "${dbName}" is a part of this cluster, set 
"teleport.dev/database_name" tag on this RDS instance to use a different name and try again.

(but if other error messages are not written this way then let it stay as it is)

i left it as is, i think we want errors to be all lower cased

[public-teleport-github-review-bot]

@kimlisa See the table below for backport results.

Branch	Result
branch/v12	Create PR
branch/v13	Create PR