Resolve "[DevOps Adoption] Migrate table to a configuration object"

What does this MR do?

This MR migrates the Devops Adoption table to an model where we can control the entire table using an object.

Screenshots (strongly suggested)

There are no visual changes here, but this MR allows us to easily modify and iterate on the DEVOPS_ADOPTION_TABLE_CONFIGURATION array, generating tables on the fly. This will be needed in order to auto build the required Dev Sec Ops tables as referenced in the related issue.

See example below;

Split configuration	Iterating the config object (instead of forcing the first index - this iteration)	Auto generated tests

Does this MR meet the acceptance criteria?

Conformity

• 📋 Does this MR need a changelog?
  • I have included a changelog entry.
  • I have not included a changelog entry because this is still behind a feature falg.
• [-] Documentation (if required)
• Code review guidelines
• [-] Merge request performance guidelines
• Style guides
• [-] Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• [-] Tested in all supported browsers
• [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• [-] 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

Related to #326480 (closed)