Use tomselect

[frcroth]

Fixes #411 and fixes #336

[coveralls]

Pull Request Test Coverage Report for Build 6817115265

• 2 of 2 (100.0%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.02%) to 74.719%

---

Totals
Change from base Build 6814675352:	-0.02%
Covered Lines:	1262
Relevant Lines:	1689

---

💛 - Coveralls

[jeriox]

lgtm!
Could you use the display name of the user instead of the username as the label field? otherwise we need to change that again with the upcoming keycloak migration as the username will be the UUID from the OIDC sub claim in the future

[jeriox]

I personally don't really like the proxy models and generally prefer substituting the user model as a whole. However, this seems to be a bit tricky for existing projects (https://docs.djangoproject.com/en/4.2/topics/auth/customizing/#changing-to-a-custom-user-model-mid-project).

[jeriox]

currently blocked as we cannot use first+last name as label

[frcroth]

Also created an issue for that: OmenApps/django-tomselect#7

[jeriox]

we looked at the code of django-tomselect and it turns out that they pass the label field name to their own js code, where it is templated to access the data in some js object. so calling a function/property on the python model is definetly not possible and using a composite label also seems quite hard. I'd vote to abandon the tomselect plan

[frcroth]

Yes, can be closed if and until there is a response to the issue

[frcroth]

There has been a response: OmenApps/django-tomselect#7 (comment)