add filter component and functionality

[emmalu]

Summary:

• What did I do?
  • Enabled the STAC catalog dropdown to allow possibility for visualizing data from multiple catalogs
  • Identified which collections in a catalog have assets, using that as a qualifier to determine if those collections have COGs that can be displayed (based on current - semi-limited lib functionality)
  • Added checkbox to control whether STAC collections in dropdown should be filtered (or not)
  • Consolidated code to set/refresh available collection items (in dropdown)
• Why *** did I do it? (What was the motivation?)
  • This was a (June 23) UWG request, to enhance the UI experience
• How *** can someone test or demo my changes?
  • Open the STAC widget and toggle the collections filter checkbox

STAC_v7_STAC_Filtered.mov

Fixes or Addresses Issue #: #66

Checklist before requesting a review:

• My code follows the guidelines of this project
• I performed a self-review of my code changes
• I have completed spell-checking, removed unnecessary print statements & commented-out code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• New and existing unit tests pass locally with my changes

[sandrahoang686]

💭 : I'm realizing that alot of these changes are probably due to the black formatter lol. But i'm thinking https://stac-browser.maap-project.org/external/ is a good candidate as a constant

[sandrahoang686]

Nice job on getting this quickly done 🙌🏼

💭 🧪 : I'm wondering when do we want to start adding tests with our changes in PRs? This change looks like it would be a good candidate to unit test but we dont have testing set up right now. I'm worried we would keep adding code and functionality creating a longer list of things to test in the future. Should we just start adding tests to our PR or we can come together and think of how to start implementing tests real soon!

[emmalu]

Nice job on getting this quickly done 🙌🏼

💭 🧪 : I'm wondering when do we want to start adding tests with our changes in PRs? This change looks like it would be a good candidate to unit test but we dont have testing set up right now. I'm worried we would keep adding code and functionality creating a longer list of things to test in the future. Should we just start adding tests to our PR or we can come together and think of how to start implementing tests real soon!

I think you're right - perhaps we should start integrating tests before the backlog of testing increases further. I do think it was important to make good progress on a feature in the interest of the overall sprint, so perhaps we can pause on implementing other features, and continue our focus to tidy-up: including testing, and perhaps some of the UI improvements we'll talk about later today.

[sandrahoang686]

lgtm