Make updating installation id a required step for cloned instances

Author: grace-rehn

src/pages/docs/administration/upgrading/guide/creating-test-instance.mdx

@@ -81,6 +81,7 @@ Creating a clone of an existing instance involves:
 1. Downloading the same version of Octopus Deploy as your main instance.
 1. Installing that version on a new server and configuring it to point to the cloned database.
 1. Copying all the files from the backed up folders from the source instance.
+1. [**Updating the Installation ID**](#update-the-instance-id) on the cloned instance (required).
 1. *Optionally*, disabling targets on the cloned instance.
 1. Download the latest version of Octopus Deploy.
 1. Upgrade the test instance to the latest version of Octopus Deploy.

src/shared-content/upgrade/upgrade-migrating-instances.include.md

@@ -2,10 +2,11 @@
 
 It will be possible to run both the old and cloned instances side by side.  Both of them can deploy to the same targets (assuming you are not using polling Tentacles).  But there are a few items to keep in mind.
 
-- The Octopus Server is tightly coupled with Calamari.  Deploying to the same target from both servers will result in Calamari getting upgraded/downgraded a lot.  
+- The Octopus Server is tightly coupled with Calamari.  Deploying to the same target from both servers will result in Calamari getting upgraded/downgraded a lot.
 - The newer Octopus Server will prompt you to upgrade the Tentacles.  While running both instances side by side, you will want to avoid this.
 - Unless the cloned instance has the same domain name, polling Tentacles will not connect to the cloned instance.  A clone of the polling Tentacles might need to be created.
 - The thumbprints for certificates and other sensitive items are stored in the Octopus Deploy database.  Cloning the database cloned those values.
+- **You must update the Installation ID on the cloned instance.** Cloning copies the Installation ID from the original, which means both instances will report [telemetry](/docs/security/outbound-requests/telemetry) under the same identifier. This corrupts usage data. See [Creating a test instance](/docs/administration/upgrading/guide/creating-test-instance) for the SQL script to generate a new Installation ID.
 
 ### Considerations
 

src/shared-content/upgrade/upgrade-update-installation-id.include.md

@@ -1,5 +1,9 @@
 ### Update the Instance ID
 
+:::div{.warning}
+**You must update the Installation ID after cloning.** Failing to do so means your cloned instance will report telemetry under the same ID as your original instance. This corrupts our usage data and prevents us from accurately understanding how many installations exist. Please do not skip this step.
+:::
+
 Cloning an instance includes the unique Installation ID of your original instance. This ID is used to identify the instance by a few integrations and sending telemetry reports.
 
 You can run this SQL Script on your cloned instance database to generate a new unique installation ID.