feat(generic): add a collections filter

[b1rger]

Closes: #1557

[gythaogg]

Exclude option is cool! Tested with nomansland, works perfectly.

UI observation - excuse me if it is an artifact of improperly configured bootstrap.
The label for "collections" looks different from other form labels. In my browser it seems to take a legend tag(because it is enclosed within a fieldset?) while other form labels use the label tag, even though all of them use the same style class form-label

[b1rger]

UI observation - excuse me if it is an artifact of improperly configured bootstrap.
The label for "collections" looks different from other form labels. In my browser it seems to take a legend tag(because it is enclosed within a fieldset?) while other form labels use the label tag, even though all of them use the same style class form-label

Ah, good catch! I had to do a lot of fiddling with the input group setup, so I totally overlooked the label. I'll have a look, maybe I can fix that

[b1rger]

UI observation - excuse me if it is an artifact of improperly configured bootstrap.
The label for "collections" looks different from other form labels. In my browser it seems to take a legend tag(because it is enclosed within a fieldset?) while other form labels use the label tag, even though all of them use the same style class form-label

Oke, so apparently this is how crispy bootstrap5 renders fieldsets. I've now set the widgets use_fieldset attribute to False, but I'm not sure if thats the right approach - it might make sense to group those elements in a fieldset, but on the other hand its only two elements. We could also set the label_class attribute on the form helper, but that would have an effect on all labels and legends.
(Maybe there is even a way to make the include/exclude select element somehow show that it refers to the collection multiselect...)

[b1rger]

UI observation - excuse me if it is an artifact of improperly configured bootstrap.
The label for "collections" looks different from other form labels. In my browser it seems to take a legend tag(because it is enclosed within a fieldset?) while other form labels use the label tag, even though all of them use the same style class form-label

Oke, so apparently this is how crispy bootstrap5 renders fieldsets. I've now set the widgets use_fieldset attribute to False, but I'm not sure if thats the right approach - it might make sense to group those elements in a fieldset, but on the other hand its only two elements. We could also set the label_class attribute on the form helper, but that would have an effect on all labels and legends.
(Maybe there is even a way to make the include/exclude select element somehow show that it refers to the collection multiselect...)

[gythaogg]

So - I can confirm that the all the labels, including collections looks uniform!