NAS-134046 / 25.04-RC.1 / Auth error in Export Key is not properly handled (by undsoft)

[bugclerk]

Automatic cherry-pick failed. Please resolve conflicts by running:

git reset --hard HEAD~1
git cherry-pick -x 8edfb86108554a9fceffda9166dac64c8d45d9ba
git cherry-pick -x 6066f1cda13dd70c81e29b5bbbb6edec4e3446b9

If the original PR was merged via a squash, you can just cherry-pick the squashed commit:

git reset --hard HEAD~1
git cherry-pick -x 84095d400815e55e27b868e9688641e9e470c209

Original issue:

1. Create a dataset with Key encryption.
2. Simulate pool.dataset.export_key failing in loadKey in ExportDatasetKeyDialogComponent.
3. Click Export Key.
   ER: I see error dialog and I am not prompted to download the key.
   AR: I see error dialog and then I am prompted to download the key.

Original PR: #11505
Jira URL: https://ixsystems.atlassian.net/browse/NAS-134046

[undsoft]

backported

[AlexKarpov98]

ported.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (stable/fangtooth@141bc6f). Learn more about missing BASE report.

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@                 Coverage Diff                 @@
##             stable/fangtooth   #11515   +/-   ##
===================================================
  Coverage                    ?   82.92%           
===================================================
  Files                       ?     1651           
  Lines                       ?    58884           
  Branches                    ?     6231           
===================================================
  Hits                        ?    48831           
  Misses                      ?    10053           
  Partials                    ?        0           

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

[bugclerk]

This PR has been merged and conversations have been locked.
If you would like to discuss more about this issue please use our forums or raise a Jira ticket.