Use `AttributePersistenceProvider`/`SafeAttributePersistenceProvider` for the storage context for server cluster interfaces

[andy31415]

This is in reference to #37851 (comment)

from #37851

We passed in PersistentStorageDelegate as a storage context for ServerClusterContext.

instead we should use an attribute persistence provider, since those are the interfaces that are supposed to be available to clusters to read/write their data.

[andy31415]

We need additional scoping and options for this issue: when checking changes in #38261 we found that:

• AttributePersistenceProvider is tightly coupled to Ember (uses ember types and native format)
• SafeAttributePersistenceProvider uses a different format and namespace from the AttributePersistenceProvider

As a result, we need a solution that both allows for ember compatibility for clusters already using ember for before (i.e. the binary data format of AttributePersistenceProvider, but without using ember metadata) as well as compatibility with 'AttributeAccessInterface' that is provider by SafeAttributePersistenceProvider.

[ratgr]

Red nodes are those that include Metadata from Ember
Yellow don't really need Ember Metadata but are linked to it
Green nodes are OK

There is no need to provide an alternative to the normal AttributePersistenceProvider as its only uses seem to be on inside ember implementations

• emAfSaveAttributeToStorageIfNeeded
• emAfLoadAttributeDefaults

[ratgr]

Red nodes are those that include Metadata from Ember
Yellow don't really need Ember Metadata but are linked to it
White Nodes don't seem to be a problem or used directly so should be able to Switch from PersistentStorageDelegate to Safe Attribute Persistent provider
Purple Nodes are ICD related and can be switched to StorageDelegateWrapper without big trouble
Green nodes are OK

There is no need to provide an alternative to the normal AttributePersistenceProvider as its only uses seem to be on inside ember implementations

After