Backport of Update gitlab-cloud-connector gem to 1.44

What does this MR do and why?

This updates the gitlab-cloud-connector gem to v1.44, which adds duo_core to the list of allowed add-ons for generate_embeddings_codebase unit primitive. This will allow SM instances with Duo Core add-ons to enable Semantic Code Search.

This needs to be backported as a bug fix to %18.8 because:

• we had documented that Semantic Code Search would be available to all tiers including Duo Core in %18.8: https://docs.gitlab.com/user/gitlab_duo/semantic_code_search/
• this is affecting a customer using the 18.8 version

Links

• Cloud Connector MR: Allow duo_core add-on for generate_embeddings_c... (gitlab-org/cloud-connector/gitlab-cloud-connector!232 - merged)
• Main MR targeting master branch: Update gitlab-cloud-connector gem to 1.44 (!222607 - merged)

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch.
• The MR that fixed the bug on the default branch has been deployed to GitLab.com (not applicable for documentation or spec changes).
• The MR title is descriptive (e.g. "Backport of 'title of default branch MR'"). This is important, since the title will be copied to the patch blog post.
• Required labels have been applied to this merge request
  • severity label and bug subtype labels (if applicable)
  • If this MR fixes a bug that affects customers, the customer label has been applied.
• This MR has been approved by a maintainer (only one approval is required).
• Ensure the e2e:test-on-omnibus-ee job has succeeded, or if it has failed, investigate the failures. If you determine the failures are unrelated, you may proceed. If you need assistance investigating, reach out to a Software Engineer in Test in #s_developer_experience.

Note to the merge request author and maintainer

If you have questions about the patch release process, please:

• Refer to the patch release runbook for engineers and maintainers for guidance.
• Ask questions on the #releases Slack channel (internal only).
• Once the backport has been merged, the commit changes will be automatically deployed to a release environment that can be used for manual validation. See after merging runbook for details.