Fix differences between access_data.yml and cloud_connector.yml

Problems

access_data.yml and cloud_connector.yml currently have different content due to recent changes in the file (see below)

To avoid potential issues we should avoid having a drift between the 2 files (documentation already recommend to update both files at the same time).

Differences:

Service Name	access_data.yml	cloud_connector.yml	Comment
duo_chat	no min_gitlab_version, no min_gitlab_version_for_free_access	min_gitlab_version: '16.3'	Expected: min_gitlab_version has no value for Gitlab.com
glab_ask_git_command	no min_gitlab_version	min_gitlab_version: '17.2'	Expected: min_gitlab_version has no value for Gitlab.com
sast	present	missing	Expected: sast service is currently available only for Gitlab.com
duo_workflow	bundled_with: _irrelevant	bundled_with: duo_enterprise	Inconsistent, but bundled_with is ignored as this feature is not sold via add_ons, and has free_access on Ultimate License
self_hosted_models	present	missing	Expected: self_hosted_models are used when we self-issue a token for self-hosted AI gateway. In that case, the SM instance is using only access_data.yml config and it does not synchronize data from CustomersDot. I
generate_description	present (missing cut_off_date)	missing	Asked here.
summarize_review	present	missing	Asked here.
analyze_ci_job_failure	No entry in vertex_ai_proxy	added	It seems this is some old experimental not used UP