Ble client fixes for proxy

[elupus]

What does this implement/fix?

• Makes sure bluetooth proxy get open failure indication (broken since Ble client additions and fixes #5277)
• Makes sure bluetooth proxy detect closes even when there are multiple virtual connections
• Removes unneeded checks from bluetooth proxy (redundant since Ble client additions and fixes #5277)

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other

Related issue or feature (if applicable): Related to #5277 and replaces #6590

Pull request in esphome-docs with documentation (if applicable): esphome/esphome-docs#

Test Environment

• ESP32
• ESP32 IDF
• ESP8266
• RP2040
• BK72xx
• RTL87xx

Example entry for config.yaml:

# Example config.yaml

Checklist:

• The code change is tested and works locally.
• Tests have been added to verify that the new code works (under tests/ folder).

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

• Documentation added/updated in esphome-docs.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 53.43%. Comparing base (4d8b5ed) to head (48104f2).
Report is 423 commits behind head on dev.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev    #6596      +/-   ##
==========================================
- Coverage   53.70%   53.43%   -0.28%     
==========================================
  Files          50       50              
  Lines        9408     9537     +129     
  Branches     1654     1685      +31     
==========================================
+ Hits         5053     5096      +43     
- Misses       4056     4130      +74     
- Partials      299      311      +12     

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

[clydebarrow]

This all looks good to me, so I guess the question is what testing has/can be done?

[probot-esphome]

Hey there @pasiz, mind taking a look at this pull request as it has been labeled with an integration (pvvx_mithermometer) you are listed as a code owner for? Thanks!
Hey there @jesserockz, mind taking a look at this pull request as it has been labeled with an integration (bluetooth_proxy) you are listed as a code owner for? Thanks!
Hey there @buxtronix, mind taking a look at this pull request as it has been labeled with an integration (am43) you are listed as a code owner for? Thanks!
Hey there @jesserockz, mind taking a look at this pull request as it has been labeled with an integration (esp32_ble_client) you are listed as a code owner for? Thanks!
Hey there @jan-hofmeier, mind taking a look at this pull request as it has been labeled with an integration (alpha3) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[elupus]

I have now tested with a "broken" config like below. Where both the proxy through HA connects to the device, as well as the ESP device itself connects to the device. Seems to work now. Previously the proxy would time out it's disconnections since no disconnection even would occure.

Admittedly, that is only a partial test of the changes here thou. The open failure indication i've not been able to figure out a testcase for.

substitutions:
  name: esp32-bluetooth-proxy-0b6900
  friendly_name: Bluetooth Proxy 0b6900
packages:
  esphome.bluetooth-proxy: github://esphome/bluetooth-proxies/esp32-generic.yaml@main
esphome:
  name: ${name}
  name_add_mac_suffix: false
  friendly_name: ${friendly_name}
api:
  encryption:
    key: ...

external_components:
  - source: github://pr#6596
    components: [ bluetooth_proxy ]

ble_client:
  - mac_address: F0:5E:CD:31:37:3E
    id:  gardena_water_switch

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

[clydebarrow]

All looks good to me.