Don't run view inlining with fast_path_optimizer

[ggevay]

This moves the inline_views call in optimize_dataflow into the non-fast_path_optimizer branch. There should be no behavior change from this, because the fast_path_optimizer bool can only be set if create_fast_path_plan already recognized a fast path opportunity before inlining, in which case not inlining is needed.

Besides a slight speedup, this also makes the code's intention more clear, i.e., that fast_path_optimizer only works when no inlining is needed.

Motivation

Tips for reviewer

Checklist

• This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
• If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.