Fix docs deployment workflow

[joshklop]

Changes:

• Install yarn symlink to the current directory and call it. This way github actions can't insert its own version of yarn.

Types of changes

What types of changes does your code introduce?

• Build related changes

Note: this is probably the fifth or sixth time we have tried to fix something related to github actions and node dependencies. If you could test it out on your end so we can avoid another PR that would be awesome (works on my end):

cd docs
rm -r node_modules
nvm use # nvm install if prompted
corepack enable yarn
yarn install
yarn start

If it builds and runs successfully, we should be good to go.

[codecov]

Codecov Report

Merging #323 (86319b0) into main (e7d92c8) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #323   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           60        60           
  Lines         6777      6775    -2     
=========================================
- Hits          6777      6775    -2     

Flag	Coverage Δ
unittests	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
pkg/crypto/weierstrass/weierstrass.go	100.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[adriantpaez]

I think we need to add the yarn and yarnpkg executables to the .gitignore file

[joshklop]

Thanks for pointing that out @adriantpaez.

I just read about the yarnPath param in the .yarnrc.yml config file and the .yarn/releases directory. With these, yarn will automatically switch to use the correct version without you needing to change anything.

This way you don't need to mess with the version on your machine. It is stored in the repository.