Feat/user recent openings new

[jazzgrewal]

Description

PR Description
Feature: Recent Openings History for the nr-silva Application

This pull request introduces a new feature that implements a browser history-like functionality for openings in the nr-silva application.

Changes Made:

User Interaction Tracking:

Whenever a user searches for openings and selects one to view, a request is sent to the backend. This interaction is logged in the user_recent_openings table within the User Preference database (PostgreSQL).
Recent Openings Dashboard:

Users can now see a "Recent Openings" table on the Openings Dashboard. This table displays the openings that the user has recently viewed, sorted by lastViewTime.
Details for each opening are fetched from the Oracle database, providing users with comprehensive information about their recent activities.
Database Modifications:

Added the necessary tables and fields in the PostgreSQL database to support the new functionality.
Frontend and Backend Integration:

This feature involves updates to both the frontend and backend components, ensuring seamless interaction and data flow between the two. By implementing this feature, we enhance user experience by allowing users to easily track and revisit their recently viewed openings.

Fixes # (issue)
This feature addresses the following tickets:

SILVA-524: https://apps.nrs.gov.bc.ca/int/jira/browse/SILVA-524
SILVA-534: https://apps.nrs.gov.bc.ca/int/jira/browse/SILVA-534
SILVA-537: https://apps.nrs.gov.bc.ca/int/jira/browse/SILVA-537

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Tested Locally Docker Compose
• Unit Tests for React components

Checklist

• I have read the CONTRIBUTING doc
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have already been accepted and merged

Further comments

---

Thanks for the PR!

Any successful deployments (not always required) will be available below.

Backend: https://nr-silva-431-backend.apps.silver.devops.gov.bc.ca/actuator/health
Frontend: https://nr-silva-31-frontend.apps.silver.devops.gov.bc.ca

Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow

---

Thanks for the PR!

Any successful deployments (not always required) will be available below.

Backend: https://nr-silva-431-backend.apps.silver.devops.gov.bc.ca/actuator/health
Frontend: https://nr-silva-31-frontend.apps.silver.devops.gov.bc.ca

Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow

[DerekRoberts]

What does this PR achieve? Is there an issue number, since this one hasn't been provided yet?

If the PR isn't ready for review please change status to draft.

[paulushcgcj]

There a few things that can be improved yet. I will check out the code later to test a few other things as well

Addressed