No longer use UI Filter starting from Installed tab

[donnie-msft]

Fixes: NuGet/Home#10510

Regression? Last working version: Yes, 16.9 regression

Description

For a bug fix (#3864) I switched back to passing the Version property in the Updates tab. However, if Installed tab is loaded first, then a UI filter is applied, Version will not bet set to "Latest Version", so it results in an incorrect or broken update action.

This PR takes the simplest approach for 16.9 and no longer uses the first-load of Installed data as a perf improvement for Updates tab.

UI Filter Scenarios:

• Updates tab loaded first, switch to Installed tab.
• Installed tab loaded first, switch to Updates tab. (this PR disables)
• After both Installed/Updates have loaded once, switching between them repetitively.

The expected Error is shown, when opening PMUI to Installed tab, switching to Updates tab, then performing an Update all:

PR Checklist

• PR has a meaningful title

• PR has a linked issue.

• Described changes

• Tests

  • Automated tests added
  • OR
  • Test exception - This is a code-behind change. I believe the Issue's indication that an Update error message indicates that no update occurred is appropriate, and that's already tested. Create an APEX test for Update all when Installed tab already loaded Home#10514
  • OR
  • N/A

• Documentation

  • Documentation PR or issue filled
  • OR
  • N/A

[dtivel]

After talking through this change with @donnie-msft, this change makes sense; however, it's an unintuitive change. Naively, I initially guessed that reverting the LatestVersion -> Version change (see the original issue) would be the fix, but Version already means different things to different tabs. Should we update comments on those properties to explain this?

Furthermore, I wouldn't expect that the Installed tab displaying first is crucial to reproducing this Updates tab bug. There is a UI test hole here which we should look at fixing after 16.9. (Thanks for creating NuGet/Home#10514.)