Configurable join type for implicit joins

Nobody has claimed this yet.

**What problem will this feature request solve?**
Currently, Metabase always generates a LEFT JOIN when fields from an implicitly joined dimension table are used in the Query Builder.

There is no way to configure the join type, which may create performance limitations. Actual example from customer:
> In Amazon Redshift, LEFT JOIN can prevent Automatic Query Rewriting (AQR) from matching queries against materialized views.
> An INNER JOIN would allows AQR to occur. This means that the current behavior blocks materialized view matching and has measurable performance impact on large fact tables.

**Describe the solution you'd like.**
Allow configuring the implicit join type to be set per foreign key relationship in the Admin → Data Model section.

**How does this feature request impact you?**
Customer request

**Additional information**
Having join strategy configurable per foreign key would enable performance optimization for warehouse related use cases.

Start in Admin → Data Model and trace how implicit joins are generated when Query Builder fields come from a dimension table. Determine how a join type could be stored per foreign key relationship and applied to those joins. Done means users can configure the type per relationship and generated queries use that setting.

Written by the indexing model from the issue text.