Update ghcr.io/projectnessie/nessie Docker tag to v0.90.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
ghcr.io/projectnessie/nessie	final	minor	0.83.2 -> 0.90.0
ghcr.io/projectnessie/nessie		minor	0.83.2 -> 0.90.0

---

Release Notes

projectnessie/nessie (ghcr.io/projectnessie/nessie)

v0.90.0

Highlights

• Nessie has got support for Iceberg REST.
• MySQL users can now configure the JDBC connection using the quarkus.datasource.mysql.*
  properties. Also, JDBC URLs can now use the mysql prefix, e.g.
  jdbc:mysql://example.com:3306/my_db.

Upgrade notes

• Helm chart: the cassandra section now has support for pulling credentials from a secret. The
  old cassandra.auth.username and cassandra.auth.password properties still work, but are now
  deprecated and will be removed in a future release. Use the cassandra.secret property instead.

New Features

• Support for Iceberg REST is in "beta" state. We appreciate early feedback, comments and suggestions.
  Take a look at the Guides and Docs
  on our web site projectnessie.org for more information.
• CEL access check scripts now receive the variable roles that can be used to check whether the current
  principal has a role assigned using a CEL expression like 'rolename' in roles.

Deprecations

• Support for Java 8 is officially deprecated and users are encouraged to upgrade all clients to
  at least Java 11, better Java 17 or 21, if possible. Current Spark versions 3.3, 3.4 and 3.5
  work with Java 11 and 17. Support for Java 8 will eventually be removed.
• For JDBC version stores, the following settings, which never worked as expected, are now
  deprecated and will be removed in a future release. The catalog and the schema must always be
  specified explicitly in the JDBC URL.
  • nessie.version.store.persist.jdbc.catalog
  • nessie.version.store.persist.jdbc.schema

Fixes

• A bug in the API compatibility filter has been discovered and fixed: when OAuth2 authentication is
  being used, the filter causes the OAuth2 client to close prematurely, thus triggering unauthorized
  errors. A workaround is to simply disable the filter (set nessie.enable-api-compatibility-check
  to false), but this is no longer necessary.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.