Introduce basic sanity test for MV used by Observability Integrations

[dai-chen]

Description

This PR introduces basic sanity tests for Flint Spark integration. These tests are designed to quickly capture obvious breaking changes in materialized views used by Observability Integration dashboards. The focus is to provide a safeguard against unexpected regressions in key MV functionalities. In the future, Observability Integration will need to maintain a complete set of tests to cover all dimensions, such as supported integrations, raw or aggregate MV etc.

Related Issues

#88

Check List

• Updated documentation (docs/ppl-lang/README.md)
• Implemented unit tests
• Implemented tests for combination with other commands
• New added source code should include a copyright header
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[YANG-DB]

@dai-chen this is a good idea for testing more specific use cases
I think we should prepare a more generic way to incorporate such specific use cases which are very dedicated domain use cases and not sufficiently general to be part of our sanity suite...

We are currently working on adding a specific docker-based framework that will allow such domain related test suites to be added - please review and let me know what you think and what would be the best way of incorporating these tests

• Docker integ test with async API #1003
• update spark-docker example with jupyter tutorial & notebook  #1001
• Created docker files for an integ test cluster (#601) #986

[dai-chen]

@dai-chen this is a good idea for testing more specific use cases I think we should prepare a more generic way to incorporate such specific use cases which are very dedicated domain use cases and not sufficiently general to be part of our sanity suite...

We are currently working on adding a specific docker-based framework that will allow such domain related test suites to be added - please review and let me know what you think and what would be the best way of incorporating these tests

• WIP: Docker integ test with async API #1003
• update spark-docker example with jupyter tutorial & notebook  #1001
• Created docker files for an integ test cluster (#601) #986

Will have a look later. Thanks!