Fix #1484: change MapperFeature.DEFAULT_VIEW_INCLUSION default to false

[cowtowncoder]

No description provided.

[cowtowncoder]

Ok this is gnarly -- about dozen test fails. Half are due to legit change (test expecting default inclusion), can just enforce "old" defaults for tests. But the rest (6 for 3.0, 5 for 2.x if I test it there) seem to be bugs in how the new setting is handled -- affects non-View enabled cases which should not be affected at all.

[cowtowncoder]

Down to 0 failures in 2.19, 2 in 3.0, getting there.

But also realizing that changing the default prevents "vanilla" processing and requires additional Active View checks -- so there is basically some overhead, both for serialization AND deserialization side. So need to do some performance verification and consider this aspect wrt defaults. :-/

[cowtowncoder]

Fixed the underlying real issue indicated by failures. So in theory this could be merged.
But need to decide whether possible performance aspect is worth worrying about or not.