SIFS write/delete/containsKey(...) exception handling does not conform to NonBlockingStore contract

Currently, when the NonBlockingSoftIndexFileStore.write(...) method fails to marshal a given key or value, it throws a PersistenceException, which is not necessarily handled by the caller (e.g. PassivationManagerImpl), which expects a CompletionStage. According to the NonBlockingStore contract, this method should instead return a CompletableFuture that has completed exceptionally.

This behavior causes regressions in WildFly - which validates that passivation of a non-marshallable cache entry will not receive a post passivation event.

The delete(...) and containsKey(...) methods have similar exception handling issues.