Idiomatic naming strategy as opt-in

[czechboy0]

Motivation

Implementation of #683.

Modifications

• Implemented the SOAR-0013 idiomatic naming strategy
• Added name overrides
• Switched most reference tests to use the new strategy
• Updated some docs (I'll update the rest after this lands and gets released, then I can update Examples and IntegrationTest)

Result

SOAR-0013 implemented.

Test Plan

Updated and added new unit tests.

[simonjbeaumont]

Thanks @czechboy0! Overall this looks good. There are a couple of things I think we should change: config management, use in tests, etc.

[simonjbeaumont]

Thanks for getting this one this far @czechboy0 :)

As per this comment and our additional discussion offline, I think we need to revisit the design of the TypeAssigner and the coupling with the naming logic.

Previously we just called into some closure which was in the context, which took no options. Now we have two strategies we've added a lot of complexity to the assigner in how it should call the closure, and since we're dealing with casing, we're also having to call the idiomatic strategy in a different way for different contexts in which it's used.

We didn't love the design before, but trying to stick with it for this feature is resulting in a lot of increased complexity and I think we should refactor to decouple the assigner and namer and create a better abstraction.

I'd personally prefer to see that as part of this PR, rather than moving things in the wrong direction temporarily.

But since this PR does add the feature we need, with the design we have, we can follow it up after.

[simonjbeaumont]

This is really nice—thanks!