Add send_on_init configuration option for KNX (#5)

[Kolbi]

• Refactor state initialization and handling in expose.py

Refactor state initialization to use current HA state and improve clarity in state management.

• Add test for binary expose initial state behavior

Add test to ensure initial state is not exposed during startup for binary sensor.

• Fix formatting in expose.py import section

• Update condition for exposing state changes

• Fix formatting in _set_expose_state method

• [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

• Parameterize core_state in test_binary_expose

• Add parameterization for core state in test_expose.py

• Refactor exposure state handling in expose.py

Refactor exposure state handling by initializing sensor values directly and removing unnecessary checks for CoreState.

• Clarify test for initial state exposure during startup

Refactor test to clarify that initial state is not exposed during startup. Adjusted comments for better understanding.

• Clarify comments in test_expose.py

Updated comments for clarity in test_expose.py.

• Refactor KNX expose tests for clarity and functionality

• [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

• Remove unused import of CoreState in test_expose.py

• Refactor test_binary_expose_does_not_send_initial_state

Removed parameterization for core_state in tests and adjusted test logic to not set the state to starting.

• Remove redundant state change in test_expose.py

Removed duplicate state change for entity_id in test.

• Potential fix for pull request finding

• Refactor test_expose.py for better async handling

• Refactor test_binary_expose to improve clarity

• Remove unnecessary assert_no_telegram calls

Removed redundant assertions for no telegrams after state changes.

• Update comment for state change exposure

• Add send_on_init configuration option for KNX

• Add send_on_init configuration option to KNX expose

• Refactor expose value initialization logic

• Add send_on_init option to KNXExposeStoreConfigModel

• [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

• Add tests for binary expose send on init feature

• Add 'send_on_init' option to KNX strings

• [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

• Update homeassistant/components/knx/expose.py

• Fix variable name for expose value initialization

• Update test to set ENTITY_ID state with brightness

Set the state of ENTITY_ID to 'on' with brightness.

• Fix comments in test_expose.py for clarity

• [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

• Rename variable 'value' to 'expose_value' for clarity

• Fix docstring formatting in expose.py

• Refactor _init_expose_state and _initialize_expose_value

• Add 'send_on_init' option to KNX strings.json

• Fix formatting in strings.json

• Fix formatting in strings.json for reset_after section

• [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

• Remove duplicate send_on_init field in expose_controller

• Remove duplicate 'send_on_init' option

• Fix duplicate definition of CONF_KNX_EXPOSE_SEND_ON_INIT

• [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

• Fix send_on_init placement in expose.py

• [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

• Remove send_on_init and update related strings

Removed 'send_on_init' option and updated its description.

• [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

---

Breaking change

Proposed change

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:
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• 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.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

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 diff between library versions and ideally a link to the changelog/release notes 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.