Update feature_category for tests with top number of queries

What does this MR do and why?

Describe in detail what your merge request does and why.

Update feature_category for tests using shared examples Update feature category for slow tests This information is added to rspec-profiling-stats reports and from here we can automatically quarantine tests and create issues for the related

Follow the progress of percentage of tests having feature_category set here

Related #386443 (closed) I'm using the folwing resources to determine the feature_category:

• https://about.gitlab.com/categories.json
• https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/data/stages.yml
• database documentation https://gitlab.com/gitlab-org/gitlab/-/tree/master/db/docs

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.