[V2] New controller manager setup

🔵 This MR is part of the implementation of Operator V2.

⚠ Rebase required before merge. Rebase after:

• !781 (closed)
• !782 (merged)

What does this MR do?

• Sets up a new Manager for Operator V2 using a scaffolding with the latest version of sigs.k8s.io/controller-runtime (see internal/cmd/manager).
• The new Manager can run with manager start command (see cmd/manager/start.go)
• The settings package outlines a mechanism to define, configure, and access to the settings of Operator V2 using github.com/spf13/viper.

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

• Merge Request Title and Description are up to date, accurate, and descriptive
• MR targeting the appropriate branch
• MR has a green pipeline on GitLab.com
• When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow

Expected (please provide an explanation if not completing)

• Test plan indicating conditions for success has been posted and passes
• Documentation created/updated
• Tests added
• Integration tests added to GitLab QA
• Equivalent MR/issue for omnibus-gitlab opened
• Validate potential values for new configuration settings. Formats such as integer 10, duration 10s, URI scheme://user:passwd@host:port may require quotation or other special handling when rendered in a template and written to a configuration file.