CMS-338: publish tab

[diego-oxd]

Jira Ticket

CMS-338

Description

Frontend changes

• updated publishTab page to display proper data fetched from the backend.
• The page will show a list of park-feature pairs (Features that have dates ready to be published)

Backend changes

• added 2 new endpoints:
  • /api/ready-to-publish - will return all the park-feature pairs that have dates ready to be published based on season.approved and season.readyToPublish
  • /api/publish-to-api - will do 2 things
    1. Mark all the active dates for the feature-year involved as inactive
    2. Create new records for the dates in Strapi that match what was entered in the staff portal
• added new helper methods to create, retrieve, and update data in Strapi.

Need to add 2 new environment variables:

1. STRAPI_TOKEN - strapi token to authenticate requests to the Strapi API. Generated in strapiURL/admin/settings/api-tokens
2. STRAPI_URL - the URL of the Strapi API (changes depending on the environment)