dom0-ztools: bump ZFS to 2.3.6

[rucoder]

Description

Bump OpenZFS from 2.3.3 to 2.3.6 to support kernels up to 6.19.

How to test and validate this PR

Build a live image and verify ZFS tools report version 2.3.6:

make live HV=kvm ZARCH=amd64 run-live
enter pillar
zfs --version

Changelog notes

Bump OpenZFS from 2.3.3 to 2.3.6.

PR Backports

• 16.0-stable: No, new feature
• 14.5-stable: No, new feature
• 13.4-stable: No, new feature

Checklist

• I've provided a proper description

• I've added the proper documentation

• I've tested my PR on amd64 device

• I've tested my PR on arm64 device

• I've written the test verification instructions

• I've set the proper labels to this PR

• I've checked the boxes above, or I've provided a good reason why I didn't
  check them.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 29.45%. Comparing base (2281599) to head (cabd5aa).
⚠️ Report is 361 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5684      +/-   ##
==========================================
+ Coverage   19.52%   29.45%   +9.92%     
==========================================
  Files          19       18       -1     
  Lines        3021     2417     -604     
==========================================
+ Hits          590      712     +122     
+ Misses       2310     1554     -756     
- Partials      121      151      +30     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[eriknordmark]

Run tests

But doesn't this need to be split in two PRs (one to create the new dom0-ztools, and then use the resulting hash for the OCI container in a second PR?)

[rucoder]

Run tests

But doesn't this need to be split in two PRs (one to create the new dom0-ztools, and then use the resulting hash for the OCI container in a second PR?)

Run tests

But doesn't this need to be split in two PRs (one to create the new dom0-ztools, and then use the resulting hash for the OCI container in a second PR?)

@eriknordmark since hashes are stable our CI check reports which hash is built. If conflicting PR that changes the same hash is merged first my PR would be marked as "needs rebase"

[eriknordmark]

@rucoder can you rebase this on master so we can at least get the eve-k build to work?

[rucoder]

@rucoder can you rebase this on master so we can at least get the eve-k build to work?

@eriknordmark done