Enhance system test automation for parallelism and crash configuration

[sumabai]

Description

Jira:
https://issues.redhat.com/browse/RHCEPHQE-16930
https://issues.redhat.com/browse/RHCEPHQE-16775

Fix description:
In this PR, Enhanced Setup and client IO to work on two mount points across two different clients for each subvolume for effective parallelism
Also, added modules to configure crash and check for crash and upload crash logs when exists.

Files changed/added:
Changed : systemutils, cephfs_systest_client_io, cephfs_systest_setup,tier-3_cephfs_system_test.yaml
Added: cephfs_crash_util

Logs:
Crash configuration automation logs: http://magna002.ceph.redhat.com/cephci-jenkins/cephci-run-PXU48Z/cephfs-crash-setup_0.log

Crash check and upload logs module automation :
http://magna002.ceph.redhat.com/cephci-jenkins/cephci-run-Y7AM6S
Please include Automation development guidelines. Source of Test case - New Feature/Regression Test/Close loop of customer BZs

click to expand checklist

• Create a test case in Polarion reviewed and approved.
• Create a design/automation approach doc. Optional for tests with similar tests already automated.
• Review the automation design
• Implement the test script and perform test runs
• Submit PR for code review and approve
• Update Polarion Test with Automation script details and update automation fields
• If automation is part of Close loop, update BZ flag qe-test_coverage “+” and link Polarion test

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sumabai

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

[hkadam134]

Looks good!

Can we include "check_for_crash: 1" in the config section of the YAML for each test, instead of creating individual tests specifically for crash validation? This way, the crash check can automatically happen in the finally block for every test. Just a thought!