Update to hickory-dns 0.25.1 (#42)

* Update to hickory-dns 0.25.1

* Adjustments for PR feedback

* Switched the default crypto provider to aws-lc-rs instead of ring
* Change debug to warn on multiple questions in one dns query
* Made it so aws-lc-rs & ring are not mutually exclusive

* When aws-lc-rs & ring are both enabled, use ring to match hickory

Based on hickory's source code (see link below), hickory will currently use ring
if both aws-lc-rs & ring are enabled at the same time. In order to match that
behavior, I've swapped the default.

* https://github.com/hickory-dns/hickory-dns/blob/0f44977800ca8954e86723fcc391514008d2bb1d/crates/proto/src/rustls/mod.rs#L50

* Utilize cargo-hack in CI for testing feature combinations

The aws-lc-rs feature, ring feature, or both features must be enabled in order
for the project to compile. cargo-hack's --at-least-one-of flag allows for
representing this requirement while still allowing the CI to test every
possible feature combination.

Author: remilia-dev

.github/workflows/rust.yml

@@ -14,18 +14,16 @@ jobs:
       - run: sudo apt-get update -y && sudo apt-get install -y knot-dnsutils
       - uses: dtolnay/rust-toolchain@stable
         id: "rust-toolchain"
-      - name: install cargo-all-features
-        uses: baptiste0928/cargo-install@v2
-        with:
-          crate: cargo-all-features
+      - name: install cargo-hack
+        uses: taiki-e/install-action@cargo-hack
       - uses: actions/cache@v3
         with:
           path: |
             ~/.cargo/git
             ~/.cargo/registry
             target
           key: "${{runner.os}} Rust ${{steps.rust-toolchain.outputs.cachekey}} Lock ${{hashFiles('Cargo.lock')}}"
-      - run: cargo test-all-features --locked -- --include-ignored
+      - run: cargo hack test --feature-powerset --at-least-one-of aws-lc-rs,ring --locked -- --include-ignored
         env:
           RUST_BACKTRACE: 1