Swap ordering to ensure Dynamic always first

[d-little]

SUMMARY

I found myself having trouble with this documentation during my own self-learning. The inconsistent order of references to dynamic/include vs. static/import caused me to keep scrolling back up to check if include was Dynamic or Static, and the same with 'which is import'.

This PR simply re-orders a few dotpoints and references to ensure that Dynamic/Include is always mentioned before Static/Import in a consistent manner. This should help to re-enforce which is which without scrolling throughout the page.

I chose Dynamic to be 'first' as the first paragraph refers to 'Dynamic vs. Static' with the footnote tagged as _dynamic_vs_static.

ISSUE TYPE

Docs Pull Request

COMPONENT NAME

playbooks_reuse.rst

[ansibot]

cc @acozine
click here for bot help

[acozine]

This is a nice improvement @d-little, thanks. This page might do well re-organized as a table, with include_* and import_* as the columns and rows for the attributes, like dynamic/static, loops yes/no, etc. Meanwhile this change makes the page better than it was.