Fix elastic_volumes and database_persistence logic

[kosstennbl]

elastic_volumes test should fail if any of the volumes is not elastic database_persistence test should test specifically resources with mysql images and pass if condition is true for all of them. This commit should fix that.
Fixes: #1884

Description

Redesigned these tests according to the discussion in the #1884.
database_persistence is tested on bitnami/mysql helm chart (i don't have possibility to set up elastic volumes, so i've checked that it fails with elastic_volume condition and passes without it)

Issues:

Refs: #1884

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]

@HashNuke if you'll have some free time for this - please check this PR.
also, I'll be offline on the next week, so i wouldn't be able to respond quickly.

[HashNuke]

The changes to expected messages for elastic_volumes test in specs had to be updated.

I have already made the changes in my branch that combines changes from multiple PRs (pr-1862-1893-1899-1890-1895-1869).