ci(fix): remove the need to specify cargosha256

By not pulling in dependencies from git directly we can get rid of the
need to calculate the sha and use nix builtins.

The git dependencies we used where:

 - h2 (to fix a k8s issue)
 - partition_id
 - blkid

 The changes to h2 are perhaps not needed anymore as the newer k8s
 clients should have the issue of authority IDs fixed.

 To get around the partition and blkid dependencies, I've implemented
 the required pieces myself basing it those crates which are not
 actively maintained.

release v0.8.1

Mayastor release v0.8.0

Release v0.7.1

Tag as Maystor release version v0.7.0

Apply tag for release v0.6.0

Tagging V0.5.0 release with semantic version tag

Update deployment YAML files to use 'latest' tag (openebs#423)

* Deploy files should specify mayastor images with 'latest' tag

* Update /deploy README - use "latest" tag on images

YAML files defining the deployment of Mayastor containers now use the 'latest' tag on all Mayastor supplied-images, instead of a one reflecting the repository branch or tag.

release: v0.3.0

Prepare deploy folder content for v0.2.0 staging (openebs#281)

Co-authored-by: Glenn Bullingham <[email protected]>