Generic Resource Identifiers with `ResourceIdTrait`

## Description
Merge changes from [https://github.com/ARK-Builders/arklib/pull/90](https://github.com/ARK-Builders/arklib/pull/90) into `ark-rust`, with the cryptographic and non-cryptographic methods of operation pushed behind feature flags in relevant crates.
## Motivation
Cryptographic hash functions ensure unique IDs for each resource, so there will be no need for collision handling in `fs-index`. To support non-cryptographic hash functions as well, we're proposing placing them behind feature flags.
## Implementation proposal
### Changes to `ResourceIdTrait` from [https://github.com/ARK-Builders/arklib/pull/90](https://github.com/ARK-Builders/arklib/pull/90)
- Simplified to include only methods to get `ResourceId` from path or data bytes.
```rust
pub trait ResourceIdTrait {
/// Associated type representing the hash used by this resource identifier.
type HashType: Debug; // + Other traits we want to enforce

/// Computes the resource identifier from the given file path
fn from_path>(file_path: P) -> Result;

/// Computes the resource identifier from the given bytes
fn from_bytes(data: &[u8]) -> Result;
}
```
- `ResourceId` doesn't need a field `data-size`
### The 2 features that should be available:
- `cryptographic-hash`: Uses cryptographic hash functions (e.g., `blake3`) to define `ResourceId`, enabled by default.
- `non-cryptographic-hash`: Uses non-cryptographic hash functions (e.g., `crc32fast`) for `ResourceId`.
### Commands to build
- Building for cryptographic hash: `cargo build --release`
- Building for non-cryptographic hash: `cargo build --release --workspace --features non-cryptographic-hash --no-default-features`
### Relevant crates:
- `data-resource`: Main crate exporting different `ResourceId` types based on enabled features. Implementation should cleanly export `ResourceId` with enforced `HashType` traits, avoiding impact on `fs-index`.
- `fs-index`: Handles collisions and index management if non-cryptographic hash `ResourceId` is exported by `data-resource`.
- `ark-cli`: Includes `ark collisions` command and other relevant commands if non-cryptographic hash `ResourceId` is used in `data-resource`.
## Follow up work:
- Update the CI to include sanity checks for build, clippy, formatting, and testing in both cryptographic and non-cryptographic hash modes of operation.
## Side note:
If we plan to include the `ResourceIndex::collisions()` method even for cryptographic hash functions (since some resources may have the same ID in case of identical content), we may not need feature-based compilation.