[#IP-339] Migrate fp-ts version from 1.x to 2.x

[fabriziopapi]

Update fp-ts version from 1.x to 2.x

List of Changes

Update fp-ts, io-ts, ts-commons and openapigen versions.
Fixed compilation errors due to different fp-ts 2.x version mode.
Fixed unit test compilation errors.
Refactor of saml.ts functions.

Motivation and Context

Reduce technical debt and enable dev to use new fp-ts feature.

How Has This Been Tested?

Already existing unit tests.

Types of changes

• Chore (nothing changes by a user perspective)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[pagopa-github-bot]

	Warnings
⚠️	Please include a Pivotal story at the beginning of the PR title (see below).
⚠️	This PR changes a total of 4183 LOCs, that is more than a reasonable size of 250. Consider splitting the pull request into smaller ones.

Example of PR titles that include pivotal stories:

• single story: [#123456] my PR title
• multiple stories: [#123456,#123457,#123458] my PR title

New dependencies added: @pagopa/ts-commons.

@pagopa/ts-commons

Author: https://www.pagopa.gov.it

Description: Shared TypeScript code for the IO project

Homepage: https://github.com/pagopa/io-ts-commons#readme

Created	8 months ago
Last Updated	9 days ago
License	MIT
Maintainers	5
Releases	12
Direct Dependencies	abort-controller, agentkeepalive, applicationinsights, fp-ts, io-ts, json-set-map, node-fetch and validator

README

TypeScript Commons

This module provides code shared by the projects of the
IO App
initiative.

Documentation is available here

Contributing

In the following there are instructions to build the app in your computer for development purposes.

Pre-requisites

We built a script for helping setting up the laptop, you can find it here

Otherwise, please follow the following steps:

Install NodeJS

To run the project you need to install a properly version of NodeJS.

On macOS and Linux we recommend the use of a virtual environment, such as nodenv for managing multiple versions of NodeJS.
The node version used in this project is stored in .node-version.

If you already have nodenv installed and configured on your system, the correct version node will be set when you access the app directory.

To install, follow the steps described below.

Install brew

If you do not have it already, install brew following the installation instructions in the home page.

Install nodenv

brew install nodenv

Install yarn

For the management of javascript dependencies we use Yarn.

Yarn is a node application. IF you have already installed in your system version of node compatible with yarn, you can install it as a global command with:

npm install -g yarn

Install dependencies

Install the libraries used by the project:

$ yarn install --frozen-lockfile

Run Tests

Run Unit Tests

$ yarn test

Run Lint Check

$ yarn lint

Updating/publishing online docs

$ yarn docs

Releasing a version

Release has been automatized by using Azure Pipelines.

To release a new version please go to io-ts-commons project on Azure and manually run pagopa.io-ts-commons.deploy the pipeline.
Be aware to choose the right release version between major|minor|patch

License

Generated by 🚫 dangerJS against a8547c1

[balanza]

@BurnedMarshal are we fine with latest changes?

[BurnedMarshal]

LGTM apart latest minor changes. Thanks for the huge work in this PR.