Add dev-env&test-env branches; update ROS report query; add KeyCloak login option

[chloe-yuu]

This PR includes the following updates:

1. New Branches Added:
   dev-env and test-env branches have been introduced.

2. Updated GitHub Actions Behavior:
   Format Check
   Trigger: Runs on PRs that are opened, synchronized, or reopened to any branch.
   Analysis: Evaluates the current feature branch without comparing against any other branch.

Sonar Check
PR Check: Runs on PRs opened, synchronized, or reopened to any branch. Compares the current feature branch against the target branch (e.g., dev-env).
Push Check: Runs on direct pushes to master, dev-env, and test-env branches. Analyzes the target branch directly.

Cypress/Jest Tests
Tag Trigger: Runs when a Git tag named cypress is pushed, analyzing the current feature branch.
PR Trigger: Also runs on PRs opened, synchronized, or reopened to master, dev-env, or test-env only, analyzing the current feature branch.

3. Deployment Process:
   Development Environment Deployment can be triggered in the following ways:
   By creating and merging a PR into the dev-env branch.
   Manually triggering the “OpenShift Deploy/Promotion to Dev” workflow from GitHub Actions.
   Using the Makefile command for quick, PR-free deployment.

Test Environment Deployment can only be triggered manually from the GitHub Actions tab by clicking the “Run workflow” button. This is required as test deployments depend on RFCs/approvals.

4. ROS Report:
   Updated to reflect changes based on the revised query.

SELECT DISTINCT
    ross.participant_id AS "Participant ID",
    p.body->>'firstName' AS "First Name",
    p.body->>'lastName' AS "Last Name",
    p.body->>'program' AS "Pathway",
    TO_DATE(ross.data->>'date', 'YYYY-MM-DD') AS "ROS Start Date",
    CASE 
        WHEN EXTRACT(month FROM TO_DATE(ross.data->>'date', 'YYYY-MM-DD')) = 2 
         AND EXTRACT(day FROM TO_DATE(ross.data->>'date', 'YYYY-MM-DD')) = 29
        THEN TO_DATE(ross.data->>'date', 'YYYY-MM-DD') + INTERVAL '1 year' + INTERVAL '1 day'
        ELSE TO_DATE(ross.data->>'date', 'YYYY-MM-DD') + INTERVAL '1 year'
    END AS "ROS End Date",
    TO_DATE(COALESCE(ross.data->>'startDate', ross.data->>'date'), 'YYYY-MM-DD') AS "Start Date at a Site",
    COALESCE(ross.data->>'positionType', 'Unknown') AS "Position Type",
    COALESCE(ross.data->>'employmentType', 'Unknown') AS "Specific Position Type",
    es.body->>'siteName' AS "Site of ROS",
    es.body->>'healthAuthority' AS "Health Region",
    CASE 
        WHEN EXISTS (
            SELECT 1 
            FROM participants_status ps_sub
            WHERE ps_sub.participant_id = ross.participant_id
              AND ps_sub.status = 'archived'
              AND ps_sub.data->>'type' = 'rosComplete'
              AND ps_sub.data->>'confirmed' = 'true'
              AND ps_sub.current = true
        ) THEN 'TRUE'
        ELSE 'FALSE'
    END AS "Return of Service Completed",
    COALESCE(
        (
            SELECT ps_sub.data->>'remainingInSectorOrRoleOrAnother'
            FROM participants_status ps_sub
            WHERE ps_sub.participant_id = ross.participant_id
              AND ps_sub.status = 'archived'
              AND ps_sub.data->>'type' = 'rosComplete'
              AND ps_sub.data->>'confirmed' = 'true'
              AND ps_sub.current = true
            LIMIT 1
        ),
        'Unknown'
    ) AS "Intends to Continue as HCA/MHAW Following ROS Completion"
FROM
    return_of_service_status ross
LEFT JOIN participants p ON
    ross.participant_id = p.id
LEFT JOIN employer_sites es ON
    ross.site_id = es.id;

5. Enabled KeyCloak login options on both dev and test environments to support internal and UAT testing with new test accounts

[sonarqubecloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)
14.7% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud