Use data size for delta metadata cache

[raunaqmorarka]

Description

Reduces chances of coordinator OOM by accounting
for retained size of objects in delta metadata cache.
TTL can be higher because the cached metadata is immutable
and the space occupied by it in memory is accounted for.

Additional context and related issues

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(x) Release notes are required, with the following suggested text:

## Delta Lake
* The configuration property `delta.metadata.cache-size` has been replaced by `delta.metadata.cache-max-retained-size` which makes it possible to control the memory usage of delta table metadata cache. By default, upto 5% of JVM max heap of the coordinator may be used for caching delta table metadata. ({issue}`issuenumber`)

[mosabua]

Just in general and with regards to the release notes.. this is a breaking change since you are removing a property.

[raunaqmorarka]

Just in general and with regards to the release notes.. this is a breaking change since you are removing a property.

Yes, it is a breaking change intentionally. We need users who were overriding the previous property to make a decision about how much coordinator memory they want to consume for the metadata cache. The old way could have potentially unbounded memory usage due to large transaction log jsons.

[mosabua]

Great.. please check my reworded commit message in the release notes PR ..