Move recents to advanced select filters; drop rightmost column in forms

[gjvoosten]

Show the links to recent locations, attendees, efforts and authorization groups as the first filter under the selection widget when editing a report. This puts all filters in one place, and no longer limits the list of recent items to the 6 most recent ones. It also does away with the extra empty space the table of recent items created.

Release notes

Closes #1964

User changes

• When editing a report, you can now find the recently used items under the selection filters of the corresponding input field.

Super User changes

• none

Admin changes

• none

System admin changes

• none
• anet.yml needs change
• db needs migration
• documentation has changed
• graphql schema has changed

Checklist

• Described the user behavior in PR body
• Referenced/updated all related issues
• commits follow a repo#issue: Title title format and these 7 rules
• commits have a clean history, otherwise PR may be squash-merged
• Added and/or updated unit tests
• Added and/or updated e2e tests
• Added and/or updated data migrations
• Updated documentation
• Resolved all build errors and warnings
• Opened debt issues for anything not resolved here

[cemalettin-work]

Should we also add recents tab to the advanced selects in the Engagement Information part for consistency ? I am talking about here

[gjvoosten]

Should we also add recents tab to the advanced selects in the Engagement Information part for consistency ? I am talking about here

In my opinion: no.

[cemalettin-work]

Should we also add recents tab to the advanced selects in the Engagement Information part for consistency ? I am talking about here

In my opinion: no.

Maybe a little bit more insight into why "no" would be nicer. Is it because that it is not a requested change or that that part has a conceptually different use case ?

[gjvoosten]

Should we also add recents tab to the advanced selects in the Engagement Information part for consistency ?

In my opinion: no.

Maybe a little bit more insight into why "no" would be nicer. Is it because that it is not a requested change or that that part has a conceptually different use case ?

It is not part of the story and there has been no request for it. If and when a need arises, this should be done as a separate story, as it could get quite involved. Which recents do you show there? There is currently no easy way to search inside custom fields; that would require JSON query paths etc.