fix(docker-entrypoint): startup with new search index for all existing trees

[genofire]

fix #531 and #510

[DavidMStraub]

But you're now creating search indexes for all existing trees even if you're spinning up a local single-tree instance to play around.

I think the better solution would be to just gracefully ignore the failing command (without specifying tree) in case of a multi-tree deployment, and document that search indexing must be triggered manually on demand (via API, UI, or command line).

[genofire]

based on #533 it would work for both single and multi tree, now.

[DavidMStraub]

I removed the search indexing from the entrypoint now so this is no longer needed. Thanks for bringing this up!