Returning to signed properties

I've been adding some benchmarking to Holster, which I will share next, but it's led me to review a lot of how Holster works. The thing that stood out most is timestamp signatures, which I switched to as a performance improvement, but which turn out to be fundamentally broken. This has meant returning to signed properties, which can be done in parallel anyway and with some other improvements to how signatures are generated has meant only a small performance cost.

This has required a major release, because servers should no longer accept timestamp signatures on data. Upgraded servers will continue serving existing data, they just won't accept data with old signatures. Browsers will continue to accept data with old signatures, which allows logged in users to write new signatures as they interact with existing data. Any application running Holster needs to update the browser and server versions at the same time so they can continue to exchange data.

Claude continues to find issues and then improve the code base, with many other gaps fixed in this release. This includes passwords now having stronger protection and fixing data encoding issues from user data. Some keywords and special characters previously made it through the code that caused issues for JavaScript and filenames on disk.