Regenerate api_pb2 after manual changes were added incorrectly in #5732

[jesserockz]

What does this implement/fix?

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): fixes

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.

[probot-esphome]

Hey there @OttoWinter, mind taking a look at this pull request as it has been labeled with an integration (api) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[jesserockz]

@kroimon did you manually update the api_pb_2 files in your PR #5732 instead of using the python script to auto generate them as per the file header?

I don't see any other way these line would have gone missing...

[kroimon]

Whoops,sorry...
I think I misunderstood your instructions here and generated the files using the scripts in the aioesphomeapi repository, then merged the changes manually to the esphome repository.
I still think it's confusing and error-prone that there are differences in the API definitions 🙈