Add warning about renaming connections

[davidculley]

Checklist

• I have reviewed the Content style guide so my content adheres to these guidelines.
• The topic I'm writing about is for specific dbt version(s) and I have versioned it according to the version a whole page and/or version a block of content guidelines.
• I have added checklist item(s) to this list for anything anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."
• The content in this PR requires a dbt release note, so I added one to the release notes page.

[vercel]

@davidculley is attempting to deploy a commit to the dbt-labs Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
docs-getdbt-com	✅ Ready (Inspect)	Visit Preview	Nov 14, 2024 7:47pm

[matthewshaver]

Thank you so much for this information @davidculley I just changed the format to a footnote and will get this merged ASAP. We appreciate the contributions

[davidculley]

@matthewshaver I'm glad to contribute! Is there a way to not change the SSH key (and thereby sever the connection), just because I rename the connection? Can this be implemented?

[matthewshaver]

@davidculley I've run this up to engineering. I'll let you know when they respond