feat: Initialize Horilla HRMS project with Jenkins CI/CD setup

[mjombanorman]

• Added Pipfile for package management with required dependencies.
• Created README_JENKINS.md for comprehensive Jenkins CI/CD pipeline documentation.
• Implemented docker-compose.ci.yaml for CI testing with PostgreSQL, Redis, and Elasticsearch services.
• Developed init-db.sh for initializing PostgreSQL database with necessary users and permissions.
• Created jenkins-init.sh for automating Jenkins setup and configuration.
• Added main.py as the entry point for the application.
• Established pyproject.toml for project metadata and dependencies.
• Configured pytest.ini for testing setup and coverage reporting.
• Created setup.cfg for project metadata, linting, and type checking configurations.

[gitguardian[bot]]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them. While these secrets were previously flagged, we no longer have a reference to the specific commits where they were detected. Once a secret has been leaked into a git repository, you should consider it compromised, even if it was deleted immediately. Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

[horilla-opensource]

Hi @mjombanorman — thanks for the comprehensive PR and for adding Jenkins CI/CD and the related Docker/compose files. I reviewed the changes and they look useful, but a quick note about branch layout for docker configuration:

• Our repository's default branch is v1 and we already keep the updated docker configuration for Horilla v2 in the dev/v2.0 branch. Because those v2 docker changes live in dev/v2.0, we prefer new docker-related updates that target version 2 to be applied there instead of the v1 default branch.

• Could you please update this PR so the docker/config changes target dev/v2.0 (rather than the current default)? You can:

  • Change the PR base to dev/v2.0, or
  • Rebase your branch onto dev/v2.0 and open/update the PR to target dev/v2.0, or
  • Open a new PR against dev/v2.0 with the docker/CI files from this branch.

You can review the current v2 docker configuration here: https://github.com/horilla-opensource/horilla/tree/dev/v2.0 — aligning with that layout will avoid conflicts and keep the v1 branch clean.

Thanks again for the contribution — let me know if you’d like help moving this to dev/v2.0

With Regards, Team Horilla