docs: update raw shipment sensor entity id in community templates

[Steggl]

The community template docs/community_templates/bubble_card.yaml still
references the old entity id sensor.parcel_raw_shipment_data.

Since the integration now creates the sensor as
sensor.parcel_app_parcel_raw_shipment_data, the template renders
empty for new installations (state_attr returns None).

This PR updates the entity id in the template accordingly.
Tested against v1.8.2 on Home Assistant 2026.8.

Also updates README.md and auto_entities.yaml which referenced the same old entity id (5 occurrences across 3 files).

[jmdevita]

Hey @Steggl ! Apologies for the delay in review, I was on vacation.

I was doing some research, and the entity ID didn't change in any parcel-ha release, it instead changed with Home Assistant's entity naming migration (completed around HA 2026.4), which now generates entity IDs for device-bound entities as device name + entity name. That's why you got sensor.parcel_app_parcel_raw_shipment_data on a fresh install, while anyone who set up the integration on an older HA core still has sensor.parcel_raw_shipment_data in their registry (existing entity IDs are preserved).

Regarding the templates- this fixes new installs but breaks the templates for existing users. Could you make them handle both IDs? For example, in bubble_card.yaml:

{% set raw = state_attr('sensor.parcel_app_parcel_raw_shipment_data', 'deliveries')
          or state_attr('sensor.parcel_raw_shipment_data', 'deliveries') %}

Regarding the Readme- there's no integration version to swap "v1.2.0" for, since the ID depends on which HA core version you were on when you first configured the integration. Maybe something like:

From v1.2.0 another sensor entity is added, containing raw json data from the API pull for debugging or custom templating. Its entity ID is sensor.parcel_raw_shipment_data for installs configured before roughly HA 2026.4, and sensor.parcel_app_parcel_raw_shipment_data for newer setups (check Developer Tools → States for yours). Note this sensor is disabled by default and needs to be enabled from the entity settings.

[Steggl]

Thanks for the research and the clear explanation – I hadn't realized the ID change came from HA's entity naming migration rather than the integration itself.
Agreed that the templates should handle both IDs.

Pushed an update:

• bubble_card.yaml: or fallback as you suggested
• auto_entities.yaml: resolves the existing entity once into raw_entity
  (checked via the state object so it also works while the sensor is
  unavailable) and uses it in all three places
• README: replaced the paragraph with your wording

Let me know if you'd prefer a different structure for the auto-entities template.

[jmdevita]

@Steggl thanks! All looks good, merged 🚀 I'll close #88 as this covers that work too. I'll push a new release with a few other fixes that came in as well soon!