feat: add blockstorage capabilities

The client can now make calls to /storage/blocks endpoints of Deuce
Store the content to the Block object; we should verify that ref_modified and ref_count are modifiable.

Thought: Perhaps we should add a special property to the Block object to denote whether it is a "storage" or "metadata" block origin, then use that to allow the opposite's id to be updateable (e.g storage block cannot have storage block id updated, but block id can be updated; vice versa).