Questionable use of `format: string` in schema QosProfileName

[hdamker]

Problem description

The schema definitions of QosProfileName within all APIs of QualityOnDemand and QoSBooking contain the line

format: string

which is at least questionable, as this isn't a defined format and it is redundant to type: string, as it adds no additional restriction.

Expected behavior

Decide if this line should be removed from all APIs defining or using the schema.

Alternative solution

Keep the line if it does at least no harm.

Additional context