installation: CNF Installation (7) Verify new installation process

[svteb]

Description

• New setup spec tests were introduced to verify that the installation method from [Feature] CNF Installation (6), Prepare new installation process #2161 works as intended.
• Three distinct issues were discovered and resolved:
  • Helm directories with variable depth levels could not be discovered after initialization (resolved through File.basename).
  • Configs that weren't named cnf-testsuite.yml could not be discovered after initialization (resolved by changing the name internally when copying the file).
  • Existence of manifest folder was not checked (resolved by adding an if check).
• Additionally a common point of failure was added with a failure message that was previously not present.
• The issue [Feature] Allow to specify deployment order in cnfs that have multiple deployments #2176 was also discovered during attempted deployment of sample-cnfs/sample-elk-stack which was also added in this commit and is to be used in future spec test.

For reviewers

The "validate_config" and "dummy-tag" spec tests are intentionally failing, this is because we are still blocking multiple deployments in one CNF and they are thus considered invalid, these spec tests will start passing again after #2171. A lot of new sample cnfs were added to test the new installation method making this commit look quite bloated, when reviewing just ignore whatever files that start with sample-cnfs (except for the new configs).

Issues:

Refs: #2168

How has this been tested:

• Covered by existing integration testing
• Added integration testing to cover
• Verified all A/C passes
  • develop
  • master
  • tag/other branch
• Test environment
  • Shared Packet K8s cluster
  • New Packet K8s cluster
  • Kind cluster
• Have not tested

Types of changes:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Checklist:

Documentation

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• No updates required.

Code Review

• Does the test handle fatal exceptions, ie. rescue block

Issue

• Tasks in issue are checked off

[kosstennbl]

Haven't checked the sample CNFs, but i suppose that they should work fine,
Two notes:

[kosstennbl]

LGTM,
Dummy-tag specs are preparation for step 8 and are meant to fail.
Validate_config spec is failing because of addition of multiple-deployment CNF for dummy-tag tests whilst multiple deployments are not supported yet for regular functionality of testsuite. So, CI failures are expected and don't point to any actual problems.

[martin-mat]

lgtm

[collivier]

else lgtm