chore: created push and pull_request workflows

[zrock-dev]

No US related

Description

CI/CD Automatization to run Gradle build and test tasks. Then when a PR is merged to develop produce a JAR artifact.

• What did I do?

• I've created two .yml files implementing GitHub Actions

• How did I do it?

  Created workflow files to ensure the health of the repository.

  • check-pull-request runs Gradle: test and build tasks. To ensure a PR is healthy.

  • check-push is triggered on push and has the same jobs as check-pull-request, but at the end it'll publish a JAR artifact.

• Why did I do it?

  So that we can have a metric for the health of the PR and distribute JAR versions of the library.

Type of Change

Put an x in all the boxes that apply:

• [x] ✨ New Feature (non-breaking change which adds functionality)
• [ ] 🛠️ Bug Fix (non-breaking change which fixes an issue)
• [ ] ❌ Breaking Change (fix or feature that would cause existing functionality to change)
• [ ] 🧹 Code Refactor
• [ ] ✅ Build Configuration Change
• [x] 📝 Documentation
• [ ] 🗑️ Chore

Pull Request Checklist

Put an x in all the boxes that apply:

• [x] My commit messages are detailed.
• [x] My code follows the code style of this project.
• [x] No existing features have been broken without good reason.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [ ] I have added tests to cover my changes.
• [x] All new and existing tests pass.

[teran-joseluis]

@fabianromeroclaros We already had it two of these files in this PR 8 so I am closing the old one.