Add Config History Link to Secure Config Page

What does this MR do?

This MR is meant to solve #332975 (closed)

It adds the Configuration History Link to all available tabs on the secure-config-page.

The feature is currently hidden behind a feature Flag (security_configuration_redesign). The feature Flag is tracked here.

This MR includes:

• Config History Link

The EE version of the Security Configuration Page has not been touched yet because it eventually will become obsolete.

The new Security Configuration Page will be data-driven from the Backend, to resolve the currently duplicated state of the pages and proceed with one single-source of truth in CE.

The EE version of the Security Configuration Page might include EE specific enhancements in the future.

How to reproduce

1. make sure your GDK is running in FOSS mode (gitlab-development-kit/env.runit)
2. enable security_configuration_redesign Feature Flag
3. Go to any project -> Security & Compliance -> Configuration

Screenshots (strongly suggested)

before	after

Does this MR meet the acceptance criteria?

Conformity

• I have included a changelog entry, or it's not needed. (Does this MR need a changelog?)
• [-] I have added/updated documentation, or it's not needed. (Is documentation required?)
• I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
• [-] I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
• I have self-reviewed this MR per code review guidelines.
• This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines)
• I have followed the style guides.

Availability and Testing

• I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.)
• I have tested this MR in all supported browsers, or it's not needed.
• I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.

Security

Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team