Log Message:
opa: Update to 0.53.1

Changes:
v0.53.1
This is a bug fix release.

v0.53.0
This release contains some enhancements, bugfixes, and a new builtin function.

- New built-in function `crypto.x509.parse_keypair`: Returns a key pair
  from a pair of PEM or base64 encoded strings of data.
- `http.send`: Add a new option to the `http.send` input object which
  allows policy authors to specify a retry count for executing a HTTP
  request. Retries are performed with an exponential backoff delay

v0.52.0
This release contains some enhancements, bugfixes, and a new builtin function.

### Allow Adding Labels via Discovery

Previously OPA did not allow any updates to the labels provided in the
boot configuration via the discovered (ie. service) config. This was
done to avoid breaking the discovery configuration. But there are use
cases where labels can serve as a convenient way to pass information
that could be used in policies, status updates or decision logs. This
change allows additional labels to be configured in the service config
which are then made available during runtime.

See the Discovery documentation at
<https://www.openpolicyagent.org/docs/v0.52.0/management-discovery/#limitations>
for more details.

### New Built-In Function: crypto.hmac.equal

`crypto.hmac.equal` provides a convenient way to compare hashes
generated by the MD5, SHA-1, SHA-256 and SHA-512 hashing algorithms.

See the documentation on the new built-in:

<https://www.openpolicyagent.org/docs/v0.52.0/policy-reference/#builtin-crypto-cryptohmacequal>
for all the details.

### Extend Authentication Methods Supported by OCI Downloader

Previously the OCI Downloader had support for only three types of
authentication methods, namely `Client TLS Certificates`, `Basic
Authentication` and `Bearer Token`. This change adds support for other
authentication methods such as AWS
Signature, GCP Metadata Token.

### Update Profiler Output With Number of Generated Expressions

The number of EVAL/REDO counts in the profile result are sometimes
difficult to understand. This is mainly due to the fact that the
compiler rewrites expressions and assigns the same location to each
generated expression and the profiler keys the counters by the
location. To provide more clarity, the profile output now includes the
number of generated expressions for each given expression thereby
helping to better understand the result and also how the evaluation
works.

See the Profiling documentation at
<https://www.openpolicyagent.org/docs/v0.52.0/policy-performance/#profiling>
for more details.