Is your feature request related to a problem? Please describe.
In our organisation, the ranking of search results does not correspond with user expectations. There are at least two personas that use search: people that know an exact table name so they can lookup table information; but there are also personas that search for the best table for something while they don't know the exact table name. So, for example: someone searching for "booking" will always have some source table ranked at the top (even with 0 usage) while a post-processed table called fact_booking with high usage would be better suited for this person.
I know that every org might have different requirements for the search ranking configuration; but currently the weights of entity ranking are hard coded.

Describe the solution you'd like
I would like a way to optionally override/configure ES weights/factors per entity attribute, so that we can optimize the search for our use case.

Describe alternatives you've considered
N/A

Additional context
Hardcoded weights code: https://github.com/open-metadata/OpenMetadata/blob/main/openmetadata-service/src/main/java/org/openmetadata/service/search/indexes/TableIndex.java#L116
Slack conversation: https://openmetadata.slack.com/archives/C02B6955S4S/p1699503942769939