generic-array 0 major version is being universally deprecated

[mulkieran]

We depend on it thusly:

├── sha2 v0.10.9
│   ├── cfg-if v1.0.3
│   ├── cpufeatures v0.2.17
│   └── digest v0.10.7
│       ├── block-buffer v0.10.4
│       │   └── generic-array v0.14.8
│       │       └── typenum v1.19.0
│       │       [build-dependencies]
│       │       └── version_check v0.9.5
│       └── crypto-common v0.1.6
│           ├── generic-array v0.14.8 (*)
│           └── typenum v1.19.0
├── stratisd_proc_macros v0.2.2 (pr

but we use one method directly as sha2 re-exports it:

error: use of deprecated method `sha2::digest::generic_array::GenericArray::<T, N>::as_slice`: please upgrade to generic-array 1.x
   --> src/engine/strat_engine/crypt/shared.rs:346:44
    |
346 |     let thp = BASE64URL_NOPAD.encode(array.as_slice());
    |                                            ^^^^^^^^
    |
    = note: `-D deprecated` implied by `-D warnings`
    = help: to override `-D warnings` add `#[allow(deprecated)]`

Deprecations added 2025 October 12. There is really nothing we should or can do, it's up to digest and crypto-common to bump their dependencies. When they do, our code should continue to compile fine, since the name of the relevant GenericArray method should remain the same.

[mulkieran]

For crypto-common, we probably need to wait for 0.2.0 series.

[mulkieran]

And for block-buffer 0.11.0 series.

[mulkieran]

And for sha2 0.11.0 series. These have all been a long time in development, so while assessment originally made it look like an easy drop in, it looks more difficult now. However, at this point there is nothing we can do, so we should do nothing.

[mulkieran]

The reason we do not encounter this problem with our current concrete dependencies is because our current generic-array dependency is too low to include the deprecation notices, anyway.

[mulkieran]

Nothing to do yet.