Improve Message Box anointment UX and update BSV dependencies

[Stephen-Thomson]

Description of Changes

• Improve UX around Message Box host anointment to make the process more transparent and user-controlled
• Update BSV dependencies to latest versions
• Fix type compatibility issues between wallet-toolbox packages

Message Box Anointment UX Improvements

Previously, configuring a Message Box URL would immediately trigger a spending authorization popup for an "overlay advertisement output" with no clear explanation of what triggered it. This was confusing for users.

New behavior:

• Saving a Message Box URL no longer automatically triggers anointment

• Users see clear anointment status (green "Anointed" / yellow "Not Anointed" chip)

• Explicit "Anoint Host" button with explanatory text about what anointing does

• Payments page shows anointment prompt if host is configured but not anointed

• Users can view all anointed hosts and revoke anointments as needed

• Added type assertions to fix cross-package type mismatches between wallet-toolbox and wallet-toolbox-client

Linked Issues / Tickets

None

Testing Procedure

Manual Testing

• I have added new unit tests
• All tests pass locally
• I have tested manually in my local environment

Checklist:

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have updated CHANGELOG.md with my changes
• I have run npm run doc and npm run lint one final time before requesting a review
• I have fixed all linter errors to ensure these changes are compliant with ts-standard
• I have run npm version patch so that my changes will trigger a new version to be released when they are merged

[BraydenLangley]

Removing an anointed message box host should use revokeHostAdvertisement to actually spend the token removing it from the overlay.