Adding git workflows with test matrix and common workflows

[chethanuk]

1. Adding GitHub workflows to test across various matrix while merging PR or pushing to master or even before releasing new version

          - java: 8
            hadoop: 2.7
            spark-version: 2.4.7
          - java: 8
            hadoop: 3.2
            spark-version: 3.0.2
          - java: 11
            hadoop: 3.2
            spark-version: 3.0.2
          - java: 8
            hadoop: 2.7
            spark-version: 3.0.2
          - java: 11
            hadoop: 2.7
            spark-version: 3.0.2
          - java: 8
            hadoop: 3.2
            spark-version: 3.1.1
          - java: 11
            hadoop: 3.2
            spark-version: 3.1.1
          - java: 8
            hadoop: 2.7
            spark-version: 3.1.1
          - java: 11
            hadoop: 2.7
            spark-version: 3.1.1

2. Adding workflows for some common git workflows (Github action to mark as stale and close issues) etc.

cc: @twollnik @TammoR

[twollnik]

Hi, Thanks for introducing these changes! We will have a look within the next two weeks.

[chethanuk]

Hi, Thanks for introducing these changes! We will have a look within the next two weeks.

Sure, I will update it. There are few changes, will push it in weekend [when I get some time]

[chethanuk]

@twollnik Also, When will be Spark 3.1.1 supported by deequ?

[aviatesk]

see #366

[twollnik]

This looks super useful overall, thanks! We would like to add just the testing workflow for now to keep the scope of the PR small (and to be honest because we are no github experts and don't feel comfortable maintaining a lot of github config code). Thanks!

[twollnik]

Could you please clarify why we need different python version and why do we need python at all?

[chethanuk]

Internally I had mono repo both deequ and python-deequ, I will remove it

[chethanuk]

On Side note, Having one mono repo for both is better

[twollnik]

Thanks so much for your quick reaction on this and for making changes. It will likely take some time for us to react to the updated PR, but we will get around to it!

[chethanuk]

@twollnik Any update? and Also waiting for Spark 3.1 support as well.

[chethanuk]

Ping!.

[twollnik]

Thanks for your patience on this.

@sscdotopen could you please take a look and let us know what you think about the proposed changes?