Feat/add npm ci

[julien-devatom]

Motivation

Morpho blue does not have any dependency (forge or npm). We can use the contracts in both hardhat and foundry projects.
If we want to ease Blue integrations to devs not working on Foundry, we can publish the package to npm.

However, publication to npm is a critical action that needs to have security about when and who can trigger the CI.

Solution

• The workflow can be triggered by hand.
• 've not defined an auto versioning not to have to allow the action to push on main the bumped version (security reason).
• However, it is up to the person triggering the workflow to define a correct version.
• There is a check to verify the semver format.
• I have created a GitHub environment (named npm) that is scoping the deployment to the main branch only and that requires administrators' reviewals before publishing on npm

[Rubilmax]

Just in case we ever publish ts: #561