Add '--ignore-engines' flag to 'yarn install' in dockerfile to avoid engine incompatability error

[0xpetersatoshi]

Description

A few sentences describing the overall effects and goals of the pull request's commits.
What is the current behavior, and what is the updated/expected behavior with this PR?

This PR resolves #109 by adding the --ignore-engines flag to yarn install in the development.dockerfile. Without this flag, running a script that builds the docker image throws an error related to a node engine incompatibility issue. The updated behavior is that the docker image is built without errors.

Other changes

Describe any minor or "drive-by" changes here.

N/A

Tested

An explanation of how the changes were tested or an explanation as to why they don't need to be.

In addition to pre-commit and push unit tests passing successfully, this was tested by running the ./scripts/dc-start-vault-gui script from the development-stack directory which starts the vault-gui app. Then, the app was accessed on http://localhost:5000/ and data was uploaded successfully to the vault.

Related issues

• Fixes [BUG] Dockerfile throws error when running yarn install step #109

Backwards compatibility

Brief explanation of why these changes are/are not backwards compatible.

N/A

[vercel]

@0xpetersatoshi is attempting to deploy a commit to the vana Team on Vercel.

To accomplish this, @0xpetersatoshi needs to request access to the Team.

Afterwards, an owner of the Team is required to accept their membership request.

If you're already a member of the respective Vercel Team, make sure that your Personal Vercel Account is connected to your GitHub account.