Accurately provide cr_button disabled to leo-button

[petemill]

Normally the fix should be to bind with $= to tell Polymer that isDisabled is a boolean attribute. However, the LeoButton actually seems to only work if some string value is provided. See brave/leo#690

Resolves brave/brave-browser#38542 by making the button actually disabled

Submitter Checklist:

• I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them
• There is a ticket for my issue
• Used Github auto-closing keywords in the PR description above
• Wrote a good PR/commit description
• Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
• Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
• Checked the PR locally:
  • npm run test -- brave_browser_tests, npm run test -- brave_unit_tests wiki
  • npm run presubmit wiki, npm run gn_check, npm run tslint
• Ran git rebase master (if needed)

Reviewer Checklist:

• A security review is not needed, or a link to one is included in the PR description
• New files have MPL-2.0 license header
• Adequate test coverage exists to prevent regressions
• Major classes, functions and non-trivial code blocks are well-commented
• Changes in component dependencies are properly reflected in gn
• Code follows the style guide
• Test plan is specified in PR before merging

After-merge Checklist:

• The associated issue milestone is set to the smallest version that the
  changes has landed on
• All relevant documentation has been updated, for instance:
  • https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)
  • https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs
  • https://github.com/brave/brave-browser/wiki/Fingerprinting-Protections
  • https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
  • https://github.com/brave/brave-browser/wiki/Web-Compatibility-Exceptions-in-Brave
  • https://github.com/brave/brave-browser/wiki/QA-Guide
  • https://github.com/brave/brave-browser/wiki/P3A

Test Plan:

[brave-builds]

A Storybook has been deployed to preview UI for the latest push

[brave-builds]

A Storybook has been deployed to preview UI for the latest push

[kjozwiak]

Verification PASSED on Win 11 x64 using the following build(s):

Brave | 1.68.64 Chromium: 126.0.6478.26 (Official Build) nightly (64-bit)
-- | --
Revision | d9689f56dafd3c9d8622461f6b4864053b0706aa
OS | Windows 11 Version 23H2 (Build 22631.3672)

Reproduced the original crash using the STR/Cases outlined via brave/brave-browser#38542 (comment) using 1.68.59 Chromium: 126.0.6478.17 as per the following:

reproducedCrash.mp4

Using the same STR/Cases mentioned above, ensured that Brave wasn't crashing when using 1.68.64 Chromium: 126.0.6478.26 as per the following:

FixedProfileCrash.mp4