Fixes for GButtons with disabled state

[ahmedhamidawan]

There are 2 fixes here:

Bug: GButton routes when disabled

We were able to route to the provided to or href even if the GButton was disabled. Now we prevent that by setting those values based on the disabled prop.

Bug: Transparent GButton with disabled state not obvious

A GButton with both transparent and disabled props as true did not show any visual difference. Now we enforce the color to gray in this case.

Before 🐞	After ✅

How to test the changes?

(Select all options that apply)

• I've included appropriate automated tests.
• This is a refactoring of components with existing test coverage.
• Instructions for manual testing are as follows:
  1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

• I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

[ahmedhamidawan]

Failing Selenium tests are unrelated

Failing Integration Selenium should also be unrelated:

FAILED test/integration_selenium/test_user_file_source_ftp.py::TestObjectStoreSelectionSeleniumIntegration::test_create_and_use -
selenium.common.exceptions.TimeoutException: Message: Timeout waiting on CSS selector [#user-file-sources-index] to become present.

#user-file-sources-index is a BTable

[mvdbeek]

#user-file-sources-index is a BTable

But it fails to be routed there because we don't wait for the button state to become enabled. Which was tricky to spot because of this bug 😆. That's gonna be fixed in #20131