fix: Incrementing autoscaling trigger, min CPU and max replicas

[andrea-deri]

List of Changes

• Updating minimum CPU usage, from 500m to 750m
• Updating autoscaling trigger on CPU, from 90% to 150%
• Updating maximum pod replicas, from 8 to 10

Motivation and Context

This PR contains some changes on autoscaling process on PROD environment, updating trigger on CPU with bigger values and adding more pods on maximum number of replicas.

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as
  expected)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[github-actions]

The default action is to increase the PATCH number of SEMVER. Set IGNORE-FOR-RELEASE if you want to skip SEMVER bump. BREAKING-CHANGE and NEW-RELEASE must be run from GH Actions section manually.

[github-actions]

The default action is to increase the PATCH number of SEMVER. Set IGNORE-FOR-RELEASE if you want to skip SEMVER bump. BREAKING-CHANGE and NEW-RELEASE must be run from GH Actions section manually.