[Request]: Implement resource identifier validation consistently.

[jglogan]

Feature or enhancement request details

Resource identifiers are validated inconsistently (some on client, some on server) or not at all (volumes), and allow any length identifier.

We should validate always on the server, limit identifier lengths, and ensure validation patterns are consistent with existing norms.

Resource	Current validation	Current pattern	Normative (according to Google)
container	client	[a-zA-Z0-9][a-zA-Z0-9_.-]+	[A-Za-z0-9][A-Za-z0-9_-.]{0,62}
image	server	Containerization handles imageref validation properly	lots of rules
network	none	N/A	[a-z0-9][a-z0-9_-]{0,62}
volume	server	[A-Za-z0-9][A-Za-z0-9_.-]*	[a-z0-9][a-z0-9_-]{0,62}

Code of Conduct

• I agree to follow this project's Code of Conduct