Update photos.py

[chrisns]

Proposed change

My photo library always seems to be indexing, for my purposes I don't need it to be indexed fully.
ideally this would be configurable but my python isn't good enough to figure out how you wire up the services in order to pass that through

marking this pr as draft since its absolutely not ready to merge without that at least being configurable, or perhaps the community have a good answer to why I should always expect the library to be indexed and this could cause the world to implode?

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New service (thank you!)
• New feature (which adds functionality to an existing service)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests
• Documentation or code sample

Example of code:

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:

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.
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated to README