Update user_select component to be more configurable

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

The following discussion from !64844 (merged) should be addressed:

• @viktomas started a discussion: (+8 comments)

  Would it be possible to reuse the shared component user_select.vue, instead of creating a new user select?

So basically the result of the linked MR user implementation is depicted in the next gif

The main stoppers that prevented from using generic user_select.vue were

1. there is no way to customize the query for the users' search - in the linked MR all project members are required
2. Uassigned label for the header. It would be nice to have it customizable or avoid at all.
3. no inline editing - need to create some wrapper component that will trigger the dropdown - the designs required inline search/removal. Even if we have inline search the user_select does not allow to hide the search input

Maybe there is something else but I did not investigate further.

With all that said, I think item 1&2 would be nice to fix for more universal adoption. Item 3 probably suggests totally different layout so I'm not sure it is worth implementing in the scope of the current component