Backport of 'Resolve GraphQL type mismatch in Cleanup policy type'

What does this MR do and why?

This MR backports this fix to update GraphQL int type for last_run_deleted_size. The last_run_deleted_size is the cache size in bytes that has been deleted. This field was introduced in 18.7.

The type in the db is bigint, which allows for the below values

Range: -9,223,372,036,854,775,808 to +9,223,372,036,854,775,807

The GraphQL int type allows for:

Range: -2,147,483,648 to +2,147,483,647

The GraphQL query for the virtual registry cleanup policy will fail if the deleted size is > than a size of 2,147,483,647 bytes.

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). Note: MR has been merged, but has not been deployed due to the change freeze. It is sitting on staging.
• 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.