[DOC] - Incorrect Nebari URLs listed in Deploy Nebari to <Provider> pages

[mwengren]

Preliminary Checks

• This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/nebari-dev/nebari/discussions

Summary

From testing deploying Nebari to AWS, I discovered the following:

The examples in Deploy Nebari on AWS shows the resulting deployed Nebari URL as a combination of projectname + domain, whereas it's just the domain itself that's used instead, the project_name variable is not used.

I discovered this by cross-referencing the example in Advanced Configuration, which shows the project_name of 'demo' being repeated in the value of the domain variable of 'demo.nebari.dev'. I found this after running into some issues with my deployment because I'd left off the prefix for my domain variable, thinking that project_name would be prepended.

I assume project_name could be anything, although I haven't actually tested this.

Correct example in Advanced Configuration > General Configuration Settings:

### General configuration ###
project_name: demo
namespace: dev
provider: gcp
domain: demo.nebari.dev

Incorrect example in Deploying Nebari on AWS > Deploying Nebari:

Services:
 - argo-workflows -> https://projectname.domain/argo/
 - conda_store -> https://projectname.domain/conda-store/
 - dask_gateway -> https://projectname.domain/gateway/
 - jupyterhub -> https://projectname.domain/
 - keycloak -> https://projectname.domain/auth/
 - monitoring -> https://projectname.domain/monitoring/

If this is right, I'll submit a PR to remove 'projectname' from the various provider docs that include the above example.