Refactor console logs page and friends

[JamesNK]

I really looked into what the console page is doing and why issues keep coming up. Problems I see:

• The page is reinitializing the query on every parameter update. It should only care when the selected resource changes.
• There are multiple cancellation tokens at work (one on page, on in log viewer control).
• The log viewer control seems unnessarily complex. Can be much simpler if the page pushes data into it.
• No way to cancel a resources logs subscription and then wait for it to clean up before starting new subscription. Created race conditions in state

Changes in PR:

• Only update console query if the selected resource changes. Remove hacks to ignore resizing and focus on when the query actually needs to change.
• Fix opening mobile view of the select resource dialog. I ran into this while testing and I think this is an unnoticed regression on main. I don't know when it started. Blazor was removing the selected value because it didn't match the any value in the resource list. The resource subscription event on this page changes the resource list. Improved by adding equality interfaces to bound values.
• Removed the JS display update for the select list. It doesn't appear to me to be needed anymore. I see items updating as resources are started and stop. Maybe the fix above sorted the issue out. @adamint Please double check that all scenarios are still working after it is removed.
• Simplify log viewer to accept logs given to it rather than reading from the source itself.
• Adds ConsoleLogs page test

Fixes #5691

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire-docs issue:
  • No

[adamint]

all scenarios seem ok