Add a parameter to Optimize-DbContext for fully qualifying types

[AndriySvyryd]

See #25523 (comment)

[viniciusverasdossantos]

There is an alternative solution? My domain has many entities and I have more than 400 conflicts

[ronymeyer]

There is an alternative solution? My domain has many entities and I have more than 400 conflicts

Workaround is mentioned here: #25523 (comment)

[ajcvickers]

Adding a note to help me find this in the future; fully-qualified typed for compiled model. :-)

[roji]

Just because I just saw this: should we maybe consider just always fully-qualifying? I think that's generally consider best practice in generated code (dealt with some similar issues in precompiled queries), and there's no real downside except more verbose generated code, which nobody cares about...

[AndriySvyryd]

should we maybe consider just always fully-qualifying?

Sure and we can add an opt-out instead

[roji]

FWIW it seems to be standard practice (e.g. in source generators) for generated code to just always be fully-qualified (including the global:: prefix for maximum disambiguation). Given that this is generated code and readability shouldn't be a big priority, is it worth even having an opt-out?

[AndriySvyryd]

For big models this could mean a lot of additional code, like tens of megabytes more.

[ajcvickers]

Note from triage: we should do this by default, since the code is not intended to be edited, but with a switch to turn it off due to the increase in size.