test: Set feature category for test Ldap::OmniauthCallbacksController

What does this MR do and why?

• Setting the feature category for test Ldap::OmniauthCallbacksController in order to avoid warning during test execution, see collapsed section

Click to open warnings during test execution

be rspec spec/controllers/ldap/omniauth_callbacks_controller_spec.rb
Run options: include {:focus=>true}

All examples were filtered out; ignoring {:focus=>true}

Test environment set up in 2.865796 seconds
Missing metadata feature_category: ./spec/controllers/ldap/omniauth_callbacks_controller_spec.rb:8 See https://docs.gitlab.com/ee/development/testing_guide/best_practices.html#feature-category-metadata
.Missing metadata feature_category: ./spec/controllers/ldap/omniauth_callbacks_controller_spec.rb:14 See https://docs.gitlab.com/ee/development/testing_guide/best_practices.html#feature-category-metadata
.Missing metadata feature_category: ./spec/controllers/ldap/omniauth_callbacks_controller_spec.rb:27 See https://docs.gitlab.com/ee/development/testing_guide/best_practices.html#feature-category-metadata
.Missing metadata feature_category: ./spec/controllers/ldap/omniauth_callbacks_controller_spec.rb:22 See https://docs.gitlab.com/ee/development/testing_guide/best_practices.html#feature-category-metadata
.Missing metadata feature_category: ./spec/controllers/ldap/omniauth_callbacks_controller_spec.rb:36 See https://docs.gitlab.com/ee/development/testing_guide/best_practices.html#feature-category-metadata
.Missing metadata feature_category: ./spec/controllers/ldap/omniauth_callbacks_controller_spec.rb:46 See https://docs.gitlab.com/ee/development/testing_guide/best_practices.html#feature-category-metadata
.Missing metadata feature_category: ./spec/controllers/ldap/omniauth_callbacks_controller_spec.rb:52 See https://docs.gitlab.com/ee/development/testing_guide/best_practices.html#feature-category-metadata
.Missing metadata feature_category: ./spec/controllers/ldap/omniauth_callbacks_controller_spec.rb:67 See https://docs.gitlab.com/ee/development/testing_guide/best_practices.html#feature-category-metadata
.Missing metadata feature_category: ./spec/controllers/ldap/omniauth_callbacks_controller_spec.rb:82 See https://docs.gitlab.com/ee/development/testing_guide/best_practices.html#feature-category-metadata
.Missing metadata feature_category: ./spec/controllers/ldap/omniauth_callbacks_controller_spec.rb:97 See https://docs.gitlab.com/ee/development/testing_guide/best_practices.html#feature-category-metadata
.Missing metadata feature_category: ./spec/controllers/ldap/omniauth_callbacks_controller_spec.rb:105 See https://docs.gitlab.com/ee/development/testing_guide/best_practices.html#feature-category-metadata
.

Finished in 12.17 seconds (files took 14.68 seconds to load)
11 examples, 0 failures

[TEST PROF INFO] Time spent in factories: 00:01.200 (8.1% of total time)

🛠 with ❤ at Siemens

Screenshots or screen recordings

Only test -related changes.

How to set up and validate locally

1. Execute the following test

be rspec spec/controllers/ldap/omniauth_callbacks_controller_spec.rb

2. You should not see any warnings

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.
  • Changelog entry added, if necessary
  • Documentation created/updated via this MR
  • Documentation reviewed by technical writer or follow-up review issue created
  • Tests added for this feature/bug
  • Tested in all supported browsers
  • Conforms to the code review guidelines
  • Conforms to the merge request performance guidelines
  • Conforms to the style guides
  • Conforms to the javascript style guides
  • Conforms to the database guides

Related to #370083 (closed)