Add settings to `TypeInfoDisplay` for optimal displaying of types in different contexts

[ironcev]

#7387 adds TypeInfoDisplay which provide basic flexibility in displaying types in various contexts. We want to have additional flexibility here, for example:

• Types from std prelude like Option or Vec can in many situations be displayed in error and warnings without the full path. This will very likely be the standard behavior for such types for most of the errors and warnings.
• For types from the local crate, we mostly do not want to display the crate name by default, but just in some situations.
• LSP actions can have different needs, depending on the code they generate.

For additional examples, Rust behavior can be taken as a good guiding example.

Note that the choice of display is always up to a specific use case, error or warning or LSP use case. TypeInfoDisplay should provide options to support different scenarios.