[Feedback appreciated]: Find a better way to store the signature

Currently the system stores the signature as metadata with originstamp, however this is not that great, if originstamp would stop operations, it would be impossible to verify the signatures, as we may not be able to access them. A better way to store them is required.

Ideas:
- Embed them in the file, and strip it before calculating the hash (shouldn't be that hard to implement, just need to send the signature down after signing. It would however require adding a versioning metadata filed to check if we need to pull data from originstamp or the file)
- ???

Any thoughts on this matter are appreciated

No files, tests, or entry points are named. First map where signatures are currently stored as OriginStamp metadata and how verification retrieves them, then compare the proposed embedded-signature approach with the existing versioning and hash workflow. Done requires an agreed storage design that permits verification when OriginStamp is unavailable.

Written by the indexing model from the issue text.