[HUDI-2280] Use GitHub Actions to build different scala spark versions

[xushiyan]

To save parallel jobs (limited to 10) in Azure CI, we can make use of GitHub Actions to run tasks to verify different build configurations.

Committer checklist

• Has a corresponding JIRA in PR title & commit

• Commit message is descriptive of the change

• CI is green

• Necessary doc changes done or have another open PR

• For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

[xushiyan]

@vinothchandar Does this look good? Travis can still serve in some way...
Or we can try GitHub Actions for this? as Travis may just stuck in queueing jobs forever.
The intention is to save the compute power in Azure to just run tests while handle build, checkstyle and other validations somewhere else.

[xushiyan]

@vinothchandar I've removed travis in the PR, as Travis will stuck from time to time while GA works totally fine for these 2 tasks. This PR will mark the CI cut-over : Azure for running tests and GA for building and validating project. I'm good with the cut-over, though there is a slight risk with Azure availability https://status.dev.azure.com/, which I think it's manageable.

[xushiyan]

@hudi-bot run azure

[xushiyan]

@hudi-bot run azure

[xushiyan]

@hudi-bot run azure

[vinothchandar]

@xushiyan I think this model of using github actions to build may be ok. Wondering if we should check with infra once, if thats okay. but high level, its nice since there will be green checks to make sure build is green at-least , while azure does the heavylifting

[xushiyan]

@hudi-bot run azure

[xushiyan]

@hudi-bot run azure

[xushiyan]

@vinothchandar i can send an email to notify infra. Meanwhile waiting for the azure to pass.

[hudi-bot]

CI report:

• b30c558 UNKNOWN
• 0000 Unknown: CANCELED

Bot commands

@hudi-bot supports the following commands:

• @hudi-bot run travis re-run the last Travis build
• @hudi-bot run azure re-run the last Azure build

[xushiyan]

closing this in favor of #3556