`astra db endpoints` Enhancement, trim url for client usage

[clun]

Description

When listing endpoints for a database i have a feedback.

Even if data-api endpoints returned is technically valid if you copy past the value and use it with a CLIENT you got a 502 bad gatewaym it is NOT the same link as you will get in astra PORTAL. I proposed to update to trim the end of the URL or split CURL endpoint to client endpoint.

astra db endpoints list astra_aws_us_east_2

┌────────────┬────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Endpoint   │ URL                                                                                                │
├────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ api        │ https://8460e4f1-57d5-46e7-bff0-4f7b25458a92-us-east-2.apps.astra.datastax.com                     │
│ swagger    │ https://8460e4f1-57d5-46e7-bff0-4f7b25458a92-us-east-2.apps.astra.datastax.com/api/json/swagger-ui │
│ playground │ https://8460e4f1-57d5-46e7-bff0-4f7b25458a92-us-east-2.apps.astra.datastax.com/api/playground      │
│ data-api   │ https://8460e4f1-57d5-46e7-bff0-4f7b25458a92-us-east-2.apps.astra.datastax.com/api/v1/json         │
└────────────┴────────────────────────────────────────────────────────────────────────────────────────────────────┘

[erichare]

@clun I have a draft PR up, but i wanted to check at the best naming convention here... right now we have api which is the bare url, and then swagger, playground, and data-api, each of which have suffices.

api would be the same as the client url, so i would think we only need one of these (perhaps just client, since api is ambiguous a bit? But, would we want to maintain api still for backwards compat?) and the current data-api with the suffix should be renamed curl perhaps also with an alias?

The only downside with that approach is then it doesn't say "data api" anywhere haha. Let me know what you think.