Prevent CI to be run for whole collection (ansible-collections#728)

Prevent CI to be run for whole collection

SUMMARY

Add a fake integration suite including an aliases file listing every module name with missing integration tests.
This fake suite is necessary for the new CI ansible-test-splitter behaviour. If one of the modules (listed in the aliases file) without a test suite is modified, the CI is run for the entire collection since the ansible-test-splitter won't find any target match. This fake integration suite helps handle this situation by avoiding running the CI for the whole collection. Furthermore, since the modules listed in the aliases file are marked as disabled, tests are automatically skipped.
Track Issue: #729

ISSUE TYPE


Feature Pull Request

COMPONENT NAME

ADDITIONAL INFORMATION

Reviewed-by: Mark Chappell <None>
Reviewed-by: Alina Buzachis <None>

tests/integration/targets/legacy_missing_tests/README.md

@@ -0,0 +1,5 @@
+## Fake integration suite
+
+This is a fake integration suite including an aliases file listing every module name with missing integration tests (some of them are covered by units). 
+
+This fake suite is necessary for the new CI ansible-test-splitter behaviour. Namely, if one of the modules (listed in the aliases file) without a test suite is modified, the CI is run for the entire collection since the ansible-test-splitter won't find any target match. This fake integration suite helps handle this situation by avoiding running the CI for the whole collection. Furthermore, since the modules listed in the aliases file are marked as disabled, tests are automatically skipped.

tests/integration/targets/legacy_missing_tests/aliases

@@ -0,0 +1,7 @@
+disabled
+
+# Lookup plugins
+aws_ssm  # covered by unit tests
+
+# Callback plugin 
+aws_resource_actions