Revert "Move "out-of-scope features" to "rejected ideas""

This reverts commit 261704f.

Signed-off-by: Michał Górny <mgorny@quansight.com>

Author: mgorny

peps/pep-0817.rst

@@ -513,6 +513,21 @@ The potential for improvement can be summarized as:
     Architect at OpenTeams
 
 
+Out-of-scope features
+---------------------
+
+This PEP presents the minimal scope required to meet modern heterogenous system needs. It leaves aspects beyond the minimal scope to evolve via tools or future PEPs. A non-exhaustive list of these aspects include:
+
+- The format of a static file to select variants deterministically or
+  include variants in a ``pylock.toml`` file,
+- The list of variant providers that are vendored or re-implemented by
+  installers,
+- The specific opt-in mechanisms and UX for allowing an installer to run
+  non-vendored variant providers,
+- How to instruct build backends to emit variants through the :pep:`517`
+  mechanism.
+
+
 Prior art
 ---------
 
@@ -2391,21 +2406,6 @@ uses.
 Rejected ideas
 ==============
 
-Out-of-scope features
----------------------
-
-This PEP presents the minimal scope required to meet modern heterogenous system needs. It leaves aspects beyond the minimal scope to evolve via tools or future PEPs. A non-exhaustive list of these aspects include:
-
-- The format of a static file to select variants deterministically or
-  include variants in a ``pylock.toml`` file,
-- The list of variant providers that are vendored or re-implemented by
-  installers,
-- The specific opt-in mechanisms and UX for allowing an installer to run
-  non-vendored variant providers,
-- How to instruct build backends to emit variants through the :pep:`517`
-  mechanism.
-
-
 An approach without provider plugins
 ------------------------------------