Bump Fully Kiosk Browser to Bronze quality scale

[cgarwood]

Proposed change

Bump Fully Kiosk Browser to Bronze quality scale.

Bronze

• config-flow - Integration needs to be able to be set up via the UI
  • Uses data-description to give context to fields (Already has one for host, Add data_description for password in Fully Kiosk config flow #131222 will add password)
  • Uses ConfigEntry.data and ConfigEntry.options correctly
• test-before-configure - Test a connection in the config flow
• unique-config-entry - Don't allow the same device or service to be able to be set up twice
• config-flow-test-coverage - Full test coverage for the config flow
• runtime-data - Use ConfigEntry.runtime_data to store runtime data
• test-before-setup - Check during integration initialization if we are able to set it up correctly
• appropriate-polling - If it's a polling integration, set an appropriate polling interval
• entity-unique-id - Entities have a unique ID
• has-entity-name - Entities use has_entity_name = True
• entity-event-setup - Entities event setup
• dependency-transparency - Dependency transparency
• action-setup - Service actions are registered in async_setup
• common-modules - Place common patterns in common modules
• docs-high-level-description - The documentation includes a high-level description of the integration brand, product, or service
• docs-installation-instructions - The documentation provides step-by-step installation instructions for the integration, including, if needed, prerequisites
• docs-removal-instructions - The documentation provides removal instructions
• docs-actions - The documentation describes the provided service actions that can be used
• brands - Has branding assets available for the integration

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.