feat: allow to export project with update_project flag (#913)

* feat: allow to project update

* fix: typo

* fix: missing dot

---------

Co-authored-by: Przemyslaw Kalitowski <przemyslaw@kalitowski.com>

changelogs/fragments/filetree_create_update_project.yml

@@ -0,0 +1,3 @@
+---
+minor_changes:
+  - filetree_create able to export project with update_project state

roles/filetree_create/README.md

@@ -26,6 +26,7 @@ The following variables are required for that role to work properly:
 | `omit_id` | N/A | no | bool | Whether to create output files without objects id.|
 | `organization`| N/A | no | str | Default organization for all objects that have not been set in the source controller.|
 | `export_related_objects` | False | no | bool | Whether to export related objects (job templates related to certain workflows and the projects associated with these job templates) when a single JT or a single WFJT are being exported. |
+| `update_project_state` | False | no | bool | Whether the project should be updated after import to the target controller. |
 
 ## Dependencies
 

roles/filetree_create/templates/current_projects.j2

@@ -22,6 +22,7 @@ controller_projects:
     default_environment: "{{ current_job_templates_asset_value.summary_fields.default_environment.name }}"
 {% endif %}
     allow_override: "{{ current_projects_asset_value.allow_override }}"
+    update_project: "{{ update_project_state | default(false) }}"
     timeout: {{ current_projects_asset_value.timeout }}
 {% if query_notification_error | length > 0 %}
     notification_templates_error: