Feature request: rpc activate (via rps) should not activate and return error if AMT returns invalid UUIDs

[msbreton]

Describe the bug 🪲
Sometime AMT is in an invalid state and returns an invalid UUID. Either all 0's or other known "bad" UUIDs.
If you activate AMT in this state, and then later deactivate/reactivate once the state has been corrected, you'll get another entry
in the database and the original entry will be orphaned. Could also cause issues with one activation overwriting another if two systems in same bad state where activated.

rps activate (via rps) should not activate and return error if AMT returns invalid UUIDs such as:

• "00000000-0000-0000-0000-000000000000"
• "03000200-0400-0500-0006-000700080009"

To Reproduce 🪜
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots 🖼️
If applicable, add screenshots to help explain your problem.

AMT Device (please complete the following information): 🖥️

• OS: [e.g. Linux Kernel & Version]
• AMT Version: [e.g. 11.8.5, 12.0.45]
• AMT Configuration Mode: [e.g. Admin Control Mode or Client Control Mode]
• Network Configuration [e.g. Dynamic IP or Static IP]

Service Deployment (please complete the following information): ⛈️

• Deployment Type: [e.g. Azure, Docker, K8s]
• Node Version: [e.g. LTS 14]
• Component & Version: [e.g. RPS 2.0.0]

Additional context
Add any other context about the problem here.