Fix issue related to verification of Windows disk encryption

[gillespi314]

Issue #25723

Addresses Windows-specific issue described in this comment.

Checklist for submitter

• Changes file added for user-visible changes in changes/, orbit/changes/ or ee/fleetd-chrome/changes.
• Input data is properly validated, SELECT * is avoided, SQL injection is prevented (using placeholders for values in statements)
• Added/updated automated tests
• A detailed QA plan exists on the associated ticket (if it isn't there, work with the product group's QA engineer to add it)
• Manual QA for all new/changed functionality

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 63.61%. Comparing base (8b23ed5) to head (19e92b0).

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #25875   +/-   ##
=======================================
  Coverage   63.60%   63.61%           
=======================================
  Files        1626     1626           
  Lines      155526   155526           
  Branches     4030     4030           
=======================================
+ Hits        98923    98933   +10     
+ Misses      48803    48795    -8     
+ Partials     7800     7798    -2     

Flag	Coverage Δ
backend	64.45% <100.00%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[getvictor]

Looks good. A few nit comments on the tests.

[gillespi314]

@PezHub, I wanted to touch base with you regarding the test plan for this ticket. In addition to testing the Windows disk encryption flow itself, we should be sure to keep an eye on this in load testing. The PR modifies how we often update the hosts_disks table, which could place some incremental stress on host checkins. Let me know if you'd like to discuss.