Allow actions and priorities to be filtered by knowledge view membership

[AJamesPhillips]

Currently

• The Actions list view includes any actions from that knowledge base
• The Priorities and Priorities list views only include prioritisations, and goals/actions from the current knowledge view

Description (acceptance criteria)

• [ ] Keep the current defaults
• [ ] Add two new filter state objects, filter_actions, filter_prioritisations, these should have the following properties:
  • active: boolean
  • knowledge_view_filter: "exact" | "nested" | "whole_tree"
  • last_knowledge_view_id: string | undefined
• [ ] add a getter function to compute if a filter is active based on the current route and if that routes filter is active or not
  • [ ] Use this getter function to get the state for the ActiveFilterWarning
• [ ] In the reducers for the new state, whenever the route is already or is changing to their view e.g. actions_list, and the knowledge_view_id (subview_id) in routing args is changing, then set this to the last_knowledge_view_id
• [ ] When the view first changes to the actions_list, priorities or priorities_list view then, if the last_knowledge_view_id is different from the current knowledge_view_id (subview_id) then offer the user an option to change to this knowledge_view -> this is useful in the case that there is one knowledge view, e.g. "Meta work" that they use for capturing all prioritisations. And if they're working on a project where the actions are captured in another, then this will also be easier to change to this knowledge view.
• [ ] When the filter is active and the knowledge_view_filter is "exact", only include components from the current composed knowledge view (i.e. it and it's foundations)
• [ ] When the filter is active and the knowledge_view_filter is "nested", include components from "exact" plus those from any nested knowledge view (and their foundations, i.e. take the composed form of nested knowledge views)
• [ ] When the filter is active and the knowledge_view_filter is "whole_tree", include components from "nested" plus those from any knowledge views up to and including it's root knowledge view and all the knowledge views nested under it (again, include the foundations of all of these knowledge views, i.e. take the composed form of nested knowledge views)

Why (hypothesis)

• Will allow the user to more easily find their prioritisations
• Will allow the user to more easily find goals and actions to add to prioritisations
• Will allow the user to be warned when the prioritisations filter is active
• Will allow the user to more easily narrow their actions list

Additional possibilities

• Users may want to include everything minus one or two knowledge views.

[AJamesPhillips]

A simplified version of this is to only implement the active: boolean state and toggle between filtering by the "exact" knowledge view or including everything.

[AJamesPhillips]

Above commit 16962a9 should make it easier to build this feature of filtering by knowledge view.