Cloning a VM with a self-hosted runner blocks removal or modification of BOTH runners

Describe the bug
I had a VM with a self-hosted runner, with a tag, say "erp_prod" for production.

As ERP's can be complicated, instead of cloning data + code, we cloned the entire VM to make sure that any "monkey patches" went along with the final QA instance for production.

Doing so, however, messed up both runners. I found I could not remove one of them without removing the runner itself from GitHub.

To Reproduce
Steps to reproduce the behavior:

1. Create a VM (in our case, an EC2 VM on AWS)
2. Create a self-hosted runner. Install on VM, tag as "prod" (whatever)
3. Clone VM via AWS cloning tools.
4. Attempt to change the label from "prod" to QA
   OR:
5. Attempt to remove the runner

Expected behavior
I should be able to update the new runner with a new ID and / or label

Runner Version and Platform

Version of your runner?
Linux: actions-runner-linux-x64-2.280.3.tar.gz
Version: 2.280.3

OS of the machine running the runner? Linux

What's not working?

The issue is that you cannot make a difference in the workflow between production and QA. So, you get a 50/50 chance of actually changing production, and there's no way to override this short of logging onto the server and manually rebuilding the runner.

Please include error messages and screenshots.

Ack! Sorry I already deleted the runner and don't want to mess up QA. You get an error that the runner has to be removed, which I could only do at the control panel on Github.com. After doing that, the source VM was of course, also disabled.

I then had to recreate two runners. This means that I can't do CI/CD on either of these servers automatically.

I believe I will be able to test this again in the next week.

Job Log Output

N/A

Runner and Worker's Diagnostic Logs

N/A
I checked the _diag directory, but they were only of actual action runs, not of the