Add 'photo frame' image integration

[karwosts]

Proposed change

This is a new integration which allows the user to select a folder¹ from the media browser during config flow. The integration then creates a single image entity, which displays a random image from that folder.

This image entity can be used to then display this random image in any frontend picture card or frontend view background.

A single 'shuffle' service is implemented to choose a next random image from the folder, allowing users to implement a virtual version of a digital photo frame on dashboards.

I researched a bit if there are other ways to achieve the same objective without an integration, but it seemed like the only solutions were fairly complicated involving custom components or writing bash scripts in the filesystem. So I hope a simple easy-setup way to achieve this would be helpful.

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

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request: Documentation for photo_frame integration home-assistant.io#41725
• Link to developer documentation pull request:
• Link to frontend pull request: Allow media selector to optionally select a media directory frontend#27873
• Link to brands pull request: Brand icon for photo_frame brands#8405

Checklist

• I understand the code I am submitting and can explain how it works.
• 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
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

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.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

Footnotes

1. requires a frontend change https://github.com/home-assistant/frontend/pull/27873 ↩

[Hedda]

Will it be supported to have multiple 'photo frame' integrations installed or can it present several different directory entities/images to different frontend cards?

Use case case example is to have one photo frame in one room’s display frontend/dashboard a different directory from what is shown in other rooms frontend/dashboards

[karwosts]

Yes you can have multiple instances. Each time you add a config entry you get 1 image entity, but you can add multiple config entries with different media paths and therefore get multiple image entities, and add different image entities to different cards.