Lists Attributes

[filipvnencak]

Description of changes

This PR adds support for list-scoped attributes throughout the application, enabling attributes to be specifically assigned to and displayed within entity lists. This brings
list entities to feature parity with other entity types (folders, tasks, versions) in terms of attribute handling.

Key changes:

• Added 'list' as a new scope option in the Attribute Editor
• List attribute forms now fetch and display list-scoped attributes from the global attribute definitions
• List filter dialog now includes list-scoped attributes as filterable options
• Attributes with enum values are properly supported in list filters

Technical details

• Fetches all attributes via useGetAttributeListQuery()
• Filters by scope?.includes('list') (matching the pattern in useEntityFields.ts:128 for folders/tasks)
• Merges list-scoped attributes with passed attributes in form fields
• Stores scoped attribute values in the attrib object

Additional context

The approach maintains consistency with how attributes are handled in folder/task detail panels (useEntityFields.ts, NewEntityContext.tsx), ensuring uniform
behavior across all entity types.

[Innders]

This is a pretty awesome update!

• Inherit flag will never make sense for lists, hide checkbox for lists.

• Use correct attribute icons for the filtering. getAttributeIcon.ts useBuildFilterOptions I think you can probably reuse this function?

• Filtering by number or text should allow for custom values to added. I think this might be solved by useBuildFilterOptions maybe.

• Number fields should show the aggregate of the numbers set on the lists. If list 1 has 100 and list 2 has 200 then we should see 100 and 200 as options for the attribute.

[Innders]

• Boolean attributes should always have Yes/No options like in the overview page.

• Filters are still stored on the user object but need to be stored on the view. Look at overview logic for how this is done as it requires some converting from queryFilters to filters that work with the component. Try to use the same logic/component.

[Innders]

Sorry I was wrong about the saving of the filters. Could we please go back to saving them on the user like before.

[Innders]

Amazing, thanks!