feat: Add disabled state to interactive UI example

[FrederikBolding]

Makes a couple of improvements to the interactive UI example Snap:

• Use custom dialog type with footers instead of regular buttons
• Add a disabled parameter which disables all of the components for testing and visual inspection
• Remove broken "Get interface state" button

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.87%. Comparing base (1760a18) to head (a59ea83).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3293   +/-   ##
=======================================
  Coverage   94.87%   94.87%           
=======================================
  Files         517      517           
  Lines       11333    11335    +2     
  Branches     1748     1749    +1     
=======================================
+ Hits        10752    10754    +2     
  Misses        581      581           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Mrtenz]

Maybe just add a few disabled elements instead of a prop to disable everything?

[FrederikBolding]

Ideally we want to show each component's disabled state, it would duplicate a lot to introduce each component in its disabled state too 🤔

[FrederikBolding]

IMO it is neat that we can test the submit button being disabled too, would be kinda hard without a disabled state