Migrate CI/CD to Github actions, fix broken links examples

[albincorreya]

This PR addresses mainly the changes related to the migration of CI/CD to GitHub actions and fix broken links in the example web demos.

• CI/CD migration #72
• Fix broken links web examples #79

Cheers to @jmarcosfer for the contributions :)

[netlify[bot]]

✔️ Deploy Preview for essentiajs-pitchmelodia ready!

🔨 Explore the source changes: ed74d7240b84b24074f62b592c9aace517c80c5c

🔍 Inspect the deploy log: https://app.netlify.com/sites/essentiajs-pitchmelodia/deploys/61a3f3638960da00081217bf

😎 Browse the preview: https://deploy-preview-80--essentiajs-pitchmelodia.netlify.app

[netlify[bot]]

✔️ Deploy Preview for essentiajs-melspectrogram ready!

🔨 Explore the source changes: ed74d7240b84b24074f62b592c9aace517c80c5c

🔍 Inspect the deploy log: https://app.netlify.com/sites/essentiajs-melspectrogram/deploys/61a3f363b862e80007a15056

😎 Browse the preview: https://deploy-preview-80--essentiajs-melspectrogram.netlify.app

[albincorreya]

@jmarcosfer Sure that is also fine. We can also make a new PR for adding the new audio problem detection demo from @ljoglar :) Since this PR is mostly related to CI/CD migration and some other minor fixes to existing examples, I think it would be good to separate both additions in different PR. If we have to wait to add anything related to CI/CD, we can keep the PR open.

[albincorreya]

@jmarcosfer Btw, I just noticed that there are no pipelines running on any changes on the dev branch as I can see here. According to your setting, shouldn't it do that? Am I missing anything here?

[jmarcosfer]

@albincorreya Nope. Workflows only run on changes to source code or build config, and I don't think there have been any changes to /src or any of the main configuration files.

[albincorreya]

@jmarcosfer That make sense. Thanks for the clarification :)