Coalesce all v-select usage into one of three new select, labeled select, and multi-select components.
Additionally this updates the dropdown button component to use the
v-select lib as well.
Formatting on files i've touched.
Add translations where I found them missing in components I touched.
Fixes a lot of bugs related to dropdowns.
refactor vue select
focusing labeled select
update namespace filter to form select
update product switcher to use select
update workspace filter to use select
select should have no default placement otherwise dd is attached to body
combining and cleaning up select styles
header filter styling issues
more style cleanup
no longer need weird z-indexing after fixing dd's
lighten up scrollbar for dropdowns & dark theme
padding cleanup for header dd's
fix workload ports
input with select should use labled select or select if no label
All labeled select components using labels, otherwise select
min width and hide broswer clear button
style cleanup
Default searchable to false unless >= 10 options
rebase fixes
wip new dd button
change button dd to click action instead of nested templates
rebasing issue
close on select
remove button dropdown from keyvalue
wip
remove old button dropdown
more cleanup
fix bug where inline options would recompute
Fix borders for new style
product menu
remove button dropdown from list masthead
new namespace design
fix padding on apps nav
Adds `existing` to the install chart component ref so that charts (service in this case) can make assumptions based on presense of chart for upgrade scnearios
I didn't use mode check to do this because existing shows us if we actually have a chart in place not just a query param.
rancher/dashboard#1557
Break CruResource cancel footer logic into component
Refactor apps/install to remove CruResource, use new footer component
Add Yaml Preview to Chart Install
When working on adding the yaml preview to the chart install page i came
to the conclusion that the footer piece is all that is required out of
CruResource for that page. Chart install requires a different set of
actions on yaml save so rather than try to kluge action handeling in it
makes more sense to decouple the common elements, ie the footer and confirm cancel