minor symfony#11041 Bootstraped the documentation of Workflow options (javiereguiluz)

This PR was squashed before being merged into the 3.4 branch (closes symfony#11041).

Discussion
----------

Bootstraped the documentation of Workflow options

I'm adding the missing workflow options as reported by symfony#7525.

I'm only listing the options and their possible values. After merging, someone who knows this component must provide the actual docs for them.

Commits
-------

5bf5ebd Bootstraped the documentation of Workflow options

Author: javiereguiluz

reference/configuration/framework.rst

@@ -125,7 +125,7 @@ Configuration
   * `https_port`_
   * `resource`_
   * `strict_requirements`_
-  * `type`_
+  * :ref:`type <reference-router-type>`
 
 * `secret`_
 * `serializer`_
@@ -193,6 +193,20 @@ Configuration
   * `strict_email`_
   * `translation_domain`_
 
+* `workflows`_
+
+  * :ref:`enabled <reference-workflows-enabled>`
+  * :ref:`name <reference-workflows-name>`
+
+    * `audit_trail`_
+    * `initial_place`_
+    * `marking_store`_
+    * `places`_
+    * `supports`_
+    * `support_strategy`_
+    * `transitions`_
+    * :ref:`type <reference-workflows-type>`
+
 secret
 ~~~~~~
 
@@ -748,6 +762,8 @@ resource
 The path the main routing resource (e.g. a YAML file) that contains the
 routes and imports the router should load.
 
+.. _reference-router-type:
+
 type
 ....
 
@@ -2164,6 +2180,135 @@ lock
 The default lock adapter. If not defined, the value is set to ``semaphore`` when
 available, or to ``flock`` otherwise. Store's DSN are also allowed.
 
+workflows
+~~~~~~~~~
+
+**type**: ``array``
+
+A list of workflows to be created by the framework extension:
+
+.. configuration-block::
+
+    .. code-block:: yaml
+
+        # config/packages/workflow.yaml
+        framework:
+            workflows:
+                my_workflow:
+                    # ...
+
+    .. code-block:: xml
+
+        <!-- config/packages/workflow.xml -->
+        <?xml version="1.0" encoding="UTF-8" ?>
+        <container xmlns="http://symfony.com/schema/dic/services"
+            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+            xmlns:framework="http://symfony.com/schema/dic/symfony"
+            xsi:schemaLocation="http://symfony.com/schema/dic/services
+                http://symfony.com/schema/dic/services/services-1.0.xsd
+                http://symfony.com/schema/dic/symfony http://symfony.com/schema/dic/symfony/symfony-1.0.xsd">
+
+            <framework:config>
+                <framework:workflows>
+                    <framework:workflow
+                        name="my_workflow" />
+                </framework:workflows>
+                <!-- ... -->
+            </framework:config>
+        </container>
+
+    .. code-block:: php
+
+        // config/packages/workflow.php
+        $container->loadFromExtension('framework', [
+            'workflows' => [
+                'my_workflow' => // ...
+            ],
+        ]);
+
+.. seealso::
+
+    See also the article about :doc:`using workflows in Symfony apps </workflow>`.
+
+.. _reference-workflows-enabled:
+
+enabled
+.......
+
+**type**: ``boolean`` **default**: ``false``
+
+Whether to enable the support for workflows or not. This setting is
+automatically set to ``true`` when one of the child settings is configured.
+
+.. _reference-workflows-name:
+
+name
+....
+
+**type**: ``prototype``
+
+Name of the workflow you want to create.
+
+audit_trail
+"""""""""""
+
+**type**: ``array``
+
+initial_place
+"""""""""""""
+
+**type**: ``string`` **default**: ``null``
+
+marking_store
+"""""""""""""
+
+**type**: ``array``
+
+Each marking store can define any of these options:
+
+* ``arguments`` (**type**: ``array``)
+* ``service`` (**type**: ``string``)
+* ``type`` (**type**: ``string`` **possible values**: ``'multiple_state'`` or
+  ``'single_state'``)
+
+places
+""""""
+
+**type**: ``array``
+
+supports
+""""""""
+
+**type**: ``string`` | ``array``
+
+support_strategy
+""""""""""""""""
+
+**type**: ``string``
+
+transitions
+"""""""""""
+
+**type**: ``array``
+
+Each marking store can define any of these options:
+
+* ``from`` (**type**: ``string``)
+* ``guard`` (**type**: ``string``) a :doc:`ExpressionLanguage </components/expression_language>`
+  compatible expression to block the transition
+* ``name`` (**type**: ``string``)
+* ``to`` (**type**: ``string``)
+
+.. _reference-workflows-type:
+
+type
+""""
+
+**type**: ``string`` **possible values**: ``'workflow'`` or ``'state_machine'``
+
+Defines the kind fo workflow that is going to be created, which can be either
+a :doc:`normal workflow </workflow/usage>` or a :doc:`state machine </workflow/state-machines>`.
+
 .. _`HTTP Host header attacks`: http://www.skeletonscribe.net/2013/05/practical-http-host-header-attacks.html
 .. _`Security Advisory Blog post`: https://symfony.com/blog/security-releases-symfony-2-0-24-2-1-12-2-2-5-and-2-3-3-released#cve-2013-4752-request-gethost-poisoning
 .. _`Doctrine Cache`: http://docs.doctrine-project.org/projects/doctrine-common/en/latest/reference/caching.html