FMA version pinning doesn't change patch policy

[jkatz01]

Fleet versions

• Discovered:
• Reproduced:

Web browser and operating system:

---

💥  Actual behavior

When changing the pinned version of an FMA via the UI, the patch policy does not update to the correct version.

🛠️ Expected behavior

The version in the patch query should be the same as the active installer. If the user is set to download the latest version, the query should follow as well. If the user is pinned to a specific version, then the query should follow that as well.

🧑‍💻  Steps to reproduce

These steps:

• Have been confirmed to consistently lead to reproduction in multiple Fleet instances.
• Describe the workflow that led to the error, but have not yet been reproduced in multiple Fleet instances.

1. Create a patch policy for an FMA that has two versions available in a fleet
2. Pin the FMA to the older version
3. Observe the patch policy still uses the newer version, not the older one pinned to.

🕯️ More info (optional)

The right query to use is stored in the software_installers.patch_query row for the pinned version

[marko-lisica]

@georgekarrv I think this deserves a P2 label.