fix(db): remove redundant indices in properties

[JohannesGGE]

• Resolves: [Bug]: Redundant properties.property_index index #42588

Summary

Remove index property_index and properties_pathonly_index because properties_path_index already covers column userid and propertypath

TODO

• ...

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)

[solracsf]

Same as #43340 (comment)

[ChristophWurst]

properties_path_index is an index on (userid, propertypath). properties_pathonly_index is an index on (propertypath). The database can use properties_pathonly_index for queries on userid and userid+propertypath, but not for queries that only access propertypath.

In general, a database can use a concatenated index when searching with the leading (leftmost) columns. An index with three columns can be used when searching for the first column, when searching with the first two columns together, and when searching using all columns.

https://use-the-index-luke.com/sql/where-clause/the-equals-operator/concatenated-keys

[ChristophWurst]

properties_pathonly_index must stay

[ChristophWurst]

😎