[feature] Add support for user profiles API

[mlnm-capco]

Adds support for the following User Profile CRUD operations (documented here)

GET /api/v2/users/{user_id}/profiles
GET /api/v2/user_profiles/{profile_id}
GET /api/v2/user_profiles?identifier={identifier}
PUT /api/v2/users/{user_id}/profiles?identifier={identifier}
PUT /api/v2/user_profiles?identifier={identifier}
PUT /api/v2/user_profiles/{profile_id}
DELETE /api/v2/user_profiles/{profile_id}

[jamesforwardnwboxed]

This would be a great thing to have, @duemir @PierreBtz would you have an opportunity to get this reviewed soon? 🙌

[PierreBtz]

what's the purpose of this method?

[PierreBtz]

Thanks for the contribution and sorry for the delay in reviewing this. I'll take some time next week to work on this.
In the meantime, in the interest of speeding things up, I did a quick scan and didn't see any obvious blocker, I just have a question about one method.
I'll make a more thorough review later.

I'll also unblock the CI on this PR to have a run and make sure the test are passing. I can already tell you things will most likely fail because of the formatting, you should be able to format yourself with mvn spotless:apply. EDIT: I stand corrected, formatting is correct :)

[PierreBtz]

Thanks for the contribution!
I found minor quirks that I think we should address prior to merging, but I'm ok overall with the change.

[PierreBtz]

looks odd to use aString here where the API (public List<UserProfile> getUserProfilesForUser(long userId) {) works with a long.

[PierreBtz]

what about aligning with the UserProfile object and use an Identifier object here?

[PierreBtz]

What about renaming the variable to queryIdentifier since this is not an identifier we are passing here, but an identifier query?

[arkadiusz-dankiewicz]

Hello there! I decided to give it a little push because those changes would be great to have!
I will take care of the review changes over the next few days. Of course, if you still find the changes appealing