Description of problem:

Using the hammer command to create or update an activation key, users can input invalid release versions (any string is accepted). This causes issues when hosts try and register. It can be difficult to spot if an admin uses "7server" instead of "7Server" in a script. The "7server" will be used in the pathway for the repository url on the content host, and will give 404 errors.

Version-Release number of selected component (if applicable):
Satellite 6.8.0

How reproducible:
always

Steps to Reproduce:
1. Create an activation key with hammer command:

1. hammer activation-key create --name=testing --release-version="thisshouldntwork" --organization-id=1 --lifecycle-environment-id=1 --content-view-id=1

2. Or update with hammer:

1. hammer activation-key update --id=1 --release-version="butitdoes" --organization-id=1

Actual results:
Activation key is created with an invalid release version.

Expected results:
The API should verify if the release version is valid.

Additional info: