[llvm] [VPlan] Add additional guiding principles to docs. (PR #85688)

[Nikolay Panchenko via llvm-commits]

================
@@ -88,6 +88,33 @@ The design of VPlan follows several high-level guidelines:
    detection and formation involves searching for and optimizing instruction
    patterns.
 
+8. The adoption of VPlan components should be done as a gradual, always-on
+   refactoring to retain quality and integrate continuously.
+
+9. Gradually refactor into multiple VPlan-to-VPlan transforms to reduce
----------------
npanchen wrote:

If I understand correctly rest of it, i.e. initial VPlan should be constructed as-is and all optimizations on it should be done by transforms (optimizations), that looks good.  However, I'm also trying to map that point to #82270. Can you please also elaborate which of these principles explains moving canonical iv construction to `prepareToExecute` ?

https://github.com/llvm/llvm-project/pull/85688