Allow to leverage tags when running architecture deployment

[cjeanner]

The nfs.yml playbook is imported from the 06-deploy-edpm.yml
sub-playbook. Due to the way ansible imports things, it was leading to
an issue if we wanted to run an architecture driven deployment, with
"--tags deploy_edpm" parameter.
This deploy_edpm tag is shared between 06-deploy-edpm.yml and
06-deploy-architecure.yml playbooks, meaning it would run through both.

The exit condition in the 06-deploy-edpm.yml play was missing the check
on cifmw_architecture_scenario we usually have, leading to issues
because of undefined facts (ansible_user_dir, ansible_env) from the
compute nodes.

This patch should allow to avoid this issue in a clean way.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from cjeanner. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[softwarefactory-project-zuul]

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/6d9027f1baa6490398f0b0666d33fed3

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 06m 09s
❌ podified-multinode-edpm-deployment-crc FAILURE in 1h 01m 10s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 29m 52s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 8m 02s
✔️ cifmw-pod-pre-commit SUCCESS in 7m 14s

[github-actions]

This PR is stale because it has been for over 15 days with no activity.
Remove stale label or comment or this will be closed in 7 days.