Add CrudService and use ORM for HSM types

This MR switches to using a proper ORM for syncing HSM types (object, tier, dataset) etc with a storage backend.

It is a big change but avoids building on ad-hoc syncing which would be different for each type.

The CrudService is central - most types and sync operations happen through it, on which we can handle most types with a single web view.

A HsmAction concept is added for HSM related things (put/get data, copy/move between tiers) that don't fit a typical CRUD setup.