Move resolve views to IndexAbstractionOptions

[jfreden]

There has been several discussions on this topic since I opened #141050 and @idegtiarenko also mentioned this in #143561 (comment).

The issue is that both resolveViews and resolveAliases are in WildcardOptions but are used when resolving both concrete index pattern targets and wildcard targets. This PR moves resolveViews from IndicesOptions.WildcardOptions into a new IndicesOptions.IndexAbstractionOptions record to address this confusing inconsistency.

This is in preparation for sending resolveViews as a parameter to field caps for remote view resolving where more work will be done to serialize resolveViews and not having this in place would make for confusing code. See #143384 for more information on the upcoming serialization of resolveViews.

Note: resolveAliases is moved in a follow up PR since it's decoupled from the resolveViews changes. #143953

Note: IndicesRequest.includeDataStreams() is the same type of flag as resolveAliases and resolveViews, it controls whether data streams participate in index resolution. It's a candidate for IndexAbstractionOptions but currently lives on IndicesRequest (not IndicesOptions) and is threaded separately through IndexNameExpressionResolver.Context as a constructor parameter. Moving it would touch 60+ files and change the IndicesRequest interface. Because of how big that change would be, I have not considered doing that in this PR (or at all).

[elasticsearchmachine]

Pinging @elastic/es-security (Team:Security)

[n1v0lg]

LGTM (pending CI)