This is not the case for the moment, which can lead to errors if you have 2 quality profiles with a different case (that were created by plugins - because it is not possible through the UI).
So we should:
- make sure that one can create 2 quality profiles with just a different case (like "Foo" and "FOO").
- update the implementation of the QP API to make sure that when some code requests a quality profile by its name, the search is case-sensitive
- for instance, when the batch tries to load a QP