Patch UpdateCiMaxTotalYamlSizeBytesDefaultValue - stable branch

What does this MR do and why?

Addressing issue.

2147483647 is the max int value. Due to a mistake in merged MR, this was omitted and a migration that potentially raised an PG::NumericValueOutOfRange: ERROR: integer out of range error was introduced. This issue could only be visible for self-hosted customers.

This MR is a patch to prevent the error from being raised. In a situation that the evaluation in the migration evaluates to more than 2147483647 bytes, the value 2147483647 bytes will be set as the limit.

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 original MR has been deployed to GitLab.com (not applicable for documentation or spec changes).
• This MR has a severity label assigned (if applicable).
• This MR has been approved by a maintainer (only one approval is required).
• Ensure the e2e:package-and-test-ee job has either succeeded or been approved by a Software Engineer in Test.

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).

Screenshots or screen recordings

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

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

• I have evaluated the MR acceptance checklist for this MR.