Add ecobulles core integration logo

[jul-fls]

Proposed change

Add Ecobulles brand assets for the new Home Assistant Core integration proposed in home-assistant/core#172636.

Ecobulles already has brand assets for the existing custom integration. This PR adds the same brand assets under the core integration namespace so they are available if the Ecobulles Core integration is accepted.

Core integration PR: home-assistant/core#172636

Type of change

• Add a new logo or icon for a new core integration
• Add a missing icon or logo for an existing core integration
• Replace an existing icon or logo with a higher quality version
• Replace an existing icon or logo after a branding change
• Removing an icon or logo

Additional information

• This PR fixes or closes issue:
• Link to code base pull request: Add Ecobulles integration core#172636
• Link to documentation pull request: TODO
• Link to integration documentation on our website: TODO

Checklist

• The added/replaced image(s) are PNG
• Icon image size is 256x256px (icon.png)
• hDPI icon image size is 512x512px for (icon@2x.png)
• Logo image size has min 128px, but max 256px, on the shortest side (logo.png)
• hDPI logo image size has min 256px, but max 512px, on the shortest side (logo@2x.png)

[jul-fls]

Hi,

I’m currently working on adding Ecobulles as a Home Assistant Core integration.

Ecobulles already exists today as a custom integration, also maintained by me, and the brand assets are already present under custom_integrations/ecobulles. My goal with this PR is to reuse the same logo/icon assets for the new Core integration, so users moving from the former custom integration to the future Core integration keep the same branding.

However, the CI currently fails because ecobulles exists in both custom_integrations and core_integrations:

The integration ecobulles exists in both core and custom integrations. Core wins.

I understand why duplicate entries are not allowed, but I’m not fully sure what the preferred migration workflow is in this case.

Should I:

move the existing assets from custom_integrations/ecobulles to core_integrations/ecobulles in this PR,
wait until the Home Assistant Core integration PR is merged before moving them,
or handle the custom integration branding separately during the transition?

The intent is not to create a conflicting duplicate entry, but to prepare the branding for the Core integration while keeping the transition clean for existing users of the custom integration.

Any guidance on the preferred approach would be appreciated.