Fix Extend ONVIF unique ID with profile index

[frenck]

Proposed change

In #32093 unique IDs for the ONVIF integration was added by me, however, I did not take into account an ONVIF capable device that can deliver multiple cameras (e.g., by a DVR or other aggregators).

This PR adjusts the unique ID to take the camera profile index into account. I've implemented it to use the hardware mac address when using profile 0 and hardware mac address + profile index otherwise. That will ensure it isn't a breaking change for current users.

I've tested it locally by adding a ONVIF capable test camera with multiple profiles.

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)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml
camera:
  - platform: onvif
    name: my_camera
    host: 192.168.1.2
    port: 8000
    username: admin
    password: admin
  - platform: onvif
    name: my_camera
    host: 192.168.1.2
    port: 8000
    username: admin
    password: admin
    profile: 1

Additional information

• This PR fixes or closes issue: fixes ONVIF Cameras with same IP but different profile treated as one entity #33093
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• 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
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

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.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum