Add capability to programmatically configure event data collection during upgrades

Description

Currently, the gitlab_rails['initial_gitlab_product_usage_data'] setting only applies during initial installation and not during upgrades. For customers using the GitLab Operator in air-gapped environments, there's a need to programmatically control event data collection settings during both installation and upgrades.

While the setting can be configured via:

• Omnibus: Using gitlab_rails['initial_gitlab_product_usage_data']
• Operator/Helm: Using global.appConfig.initialDefaults.gitlabProductUsageData

These settings only apply during initial installation. For upgrades, customers must use the UI or rails console to change this setting.

Requirements

• Add capability to programmatically configure event data collection settings during upgrades
• Provide a consistent method to manage this setting across installation and upgrade scenarios
• Support automated deployment workflows in air-gapped environments

Additional Context

• The current workaround requires manual intervention via the UI or using gitlab-rails runner through the toolbox
• This feature is particularly important for customers deploying multiple air-gapped instances that need automated configuration management

Reference Links - !179666 (merged)

#510333 (closed)

omnibus-gitlab!8190 (merged)

gitlab-org/charts/gitlab!4250 (merged)