Fix issue with incorrect Notion bridge IDs

[bachya]

Description:

A new bug popped into the Notion API: it's possible for sensors to refer to bridge IDs that don't actually exist. Currently, this throws an exception (because each entity's device_info expects this info to be valid) and prevents that sensor from loading. This PR ensures that sensors continue to load even if they refer to a nonexistent bridge.

Related issue (if applicable): fixes #25682

Pull request with documentation for home-assistant.io (if applicable): N/A

Example entry for configuration.yaml (if applicable):

notion:
  username: !secret notion_username
  password: !secret notion_password

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist

[MartinHjelmare]

Do we need to update _update_bridge_id?

Does the entity continue to operate without a valid bridge id? Should the entity be marked unavailable when this happens?

[bachya]

@MartinHjelmare:

Do we need to update _update_bridge_id?

Great call!

Does the entity continue to operate without a valid bridge id? Should the entity be marked unavailable when this happens?

The sensors will continue to work perfectly, interestingly – ran for several hours last night and everything works as expected. Makes me think this is just an API issue, not an underlying problem.

[MartinHjelmare]

Looks good!