Update hickory-resolver

[cr-tk]

Summary & Motivation (Problem vs. Solution)

Switch to a new minor version of hickory-resolver, primarily motivated by known issues in 0.25.2.

How I Tested These Changes

CI only

Pre merge check list

TBD.

• Call out updates and breaking changes via conventional commits
• Communicate verification flow breaking changes especially thoroughly. If any of the following answers are no, then this is a verification flow breaking change:
  • Can enclaves in a previous QOS version still key forward to this new version?
  • Can previous versions of QOS verify attestations from this new version?
  • Can manifests generated by a previous version still be parsed by this one?
  • Can previous approvals still be verified against a manifest (i.e. is this a non-breaking change to the manifest signing payload)?
  • Can a previous version of QOS still perform a boot standard on an enclave of this version?

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	rand@​0.10.1
	rand_core@​0.10.0
	hickory-resolver@​0.25.2 ⏵ 0.26.1

View full report

[cr-tk]

@emostov is this ready to go out of draft mode?

[emostov]

@emostov is this ready to go out of draft mode?

Yes just needs dep review

[cr-tk]

Rebased the branch against main to account for some minor Cargo.lock changes there, which led to a merge conflict.

[cr-tk]

Drop a commit that removed dnssec-ring, which we want to keep for DNSSEC support.