fix: use Cloud Development Environment consistently in Get Started

CDE is the industry standard term. Use it in all titles and headings.
"Workspace" only when quoting exact UI labels (Workspaces page, Create
Workspace button).

- Restore "Open your project in a Cloud Development Environment" (SME)
- "How Git authentication works in Cloud Development Environments"
- "Manage your Cloud Development Environments"
- "Start a Cloud Development Environment from a raw devfile URL"
- "What can you do in a Cloud Development Environment?"
- Overview defines CDE = workspace = DevWorkspace equivalence

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: gtrivedi88

modules/get-started/pages/authenticating-to-a-git-server-from-a-workspace.adoc

@@ -1,11 +1,11 @@
 :_content-type: CONCEPT
 :description: Authenticating to a Git server from a workspace
 :keywords: authentication, authenticate, github, gitlab, bitbucket
-:navtitle: How Git authentication works in workspaces
+:navtitle: How Git authentication works in Cloud Development Environments
 :page-aliases: end-user-guide:authenticating-to-a-git-server-from-a-workspace.adoc
 
 [id="authenticating-to-a-git-server-from-a-workspace"]
-= How Git authentication works in workspaces
+= How Git authentication works in Cloud Development Environments
 
 pass:[<!-- vale RedHat.CaseSensitiveTerms = NO -->]
 

modules/get-started/pages/basic-actions-you-can-perform-on-a-workspace.adoc

@@ -1,11 +1,11 @@
 :_content-type: REFERENCE
 :description: Basic actions you can perform on a workspace
 :keywords: workspace, workspaces, reopen, restart, stop, start, delete
-:navtitle: Manage your workspaces
+:navtitle: Manage your Cloud Development Environments
 :page-aliases: end-user-guide:basic-actions-you-can-perform-on-a-workspace.adoc
 
 [id="basic-actions-you-can-perform-on-a-workspace"]
-= Manage your workspaces
+= Manage your Cloud Development Environments
 
 You manage your workspaces and verify their current states in the *Workspaces* page (`pass:c,a,q[{prod-url}]/dashboard/#/workspaces`) of your {prod-short} dashboard.
 

modules/get-started/pages/starting-a-workspace-from-a-git-repository-url.adoc

@@ -1,11 +1,11 @@
 :_content-type: PROCEDURE
 :description: Starting a workspace from a Git repository URL
 :keywords: start-new-workspace, start-a-new-workspace, how-to-start-new-workspace, how-to-start-a-new-workspace, starting-a-new-workspace, clone-git-repository, clone-a-git-repository, how-to-start-workspace, how-to-start-a-workspace
-:navtitle: Open your project in a cloud workspace
+:navtitle: Open your project in a Cloud Development Environment
 :page-aliases: end-user-guide:starting-a-workspace-from-a-git-repository-url.adoc
 
 [id="starting-a-workspace-from-a-git-repository-url"]
-= Open your project in a cloud workspace
+= Open your project in a Cloud Development Environment
 
 In the context of this procedure, "Git repository URL" refers to a git clone URL of a repository. Usually, you can fetch this URL by clicking on the *Clone* button in the SCM repository's main page.
 Alternatively, you can copy the URL from the address bar of your browser when you are on the main page of the repository.

modules/get-started/pages/starting-a-workspace-from-a-raw-devfile-url.adoc

@@ -1,11 +1,11 @@
 :_content-type: PROCEDURE
 :description: Starting a workspace from a raw devfile URL
 :keywords: start-new-workspace, start-a-new-workspace, how-to-start-new-workspace, how-to-start-a-new-workspace, starting-a-new-workspace, how-to-start-workspace, how-to-start-a-workspace
-:navtitle: Start a workspace from a raw devfile URL
+:navtitle: Start a Cloud Development Environment from a raw devfile URL
 :page-aliases: end-user-guide:starting-a-workspace-from-a-raw-devfile-url.adoc
 
 [id="starting-a-workspace-from-a-raw-devfile-url"]
-= Start a workspace from a raw devfile URL
+= Start a Cloud Development Environment from a raw devfile URL
 
 With {prod-short}, you can open a *devfile* URL in your browser to start a new workspace.
 

modules/get-started/pages/your-first-workspace.adoc

@@ -7,7 +7,7 @@
 = Your first-day experience
 
 [role="_abstract"]
-{prod-short} creates a Cloud Development Environment for your project, called a *workspace* in the dashboard and CLI. Each workspace runs as a {orch-name} `DevWorkspace` custom resource on your cluster. You go from login to coding in about three minutes.
+{prod-short} creates a Cloud Development Environment (CDE) for your project. The dashboard and CLI refer to each CDE as a *workspace*. Each Cloud Development Environment runs as a {orch-name} `DevWorkspace` custom resource on your cluster. You go from login to coding in about three minutes.
 
 include::partial$snip_persona-developer.adoc[]
 
@@ -36,7 +36,7 @@ The first workspace start takes approximately 2-3 minutes because {prod-short} p
 
 Subsequent starts are faster because {platforms-name} caches the container images on the node. If your administrator has deployed the {image-puller-name-short}, images are pre-cached across all nodes for near-instant starts.
 
-== What can you do in a workspace?
+== What can you do in a Cloud Development Environment?
 
 A running {prod-short} workspace provides: