tests: add github actions (#154)

* docs: add contributing guide, code of conduct, pr template,...

* build: add gha for testing

* build: remove lint test

* build: run gha on current branch for testing purposes

* fix: export env var SCW_REGION

* build: add test to see if secret vars are set

* tests: use projects for each test

* tests: update package.json to run tests sequentially (quotas limit)

* tests: fix function test and container private reg test

* tests: fix tests runtimes & triggers + run tests in parallel

* test: add package.json forgotten in previous commit

* tests: fix failing tests (maybe)

* tests: fix test triggers

* tests: add runInBand option to run test

* tests: set --maxWorkers to 4

* tests: try/catch for creating projects

* tests: remove inline var

* tests: try to fix them

* tests: try to fix the fix

* tests: update package.json to load env var

* tests: fix ?

* tests: set maxWorkers to 4 fix credentials errors ?

* fix(tests): resolve pending promise

* tests: fix containers_private_registry test

* tests: remove bail option

* tests: in runtime tests, only retrieve directories (e.g. exclude README.md file)

* tests: remove afterAll clean-up temporarily

* tests: replace registryApi to use containerApi

* tests: add method to delete project by id

* tests: remove logs for cleanup

* tests: log error in execSync

* tests: change secret SCW_REGION to var

* chore: upgrade jest version

* tests: remove afterAll and add globalTeardown

* tests: add global teardown

* tests(fix): add missing s to test

* tests: fix

* tests: use jest-circus runner

* tests: add --no-cache option

* tests: refacto clean-up

* tests: remove globalTeardown and use new gha instead

* tests: remove workerThreads option

* tests: remove require clean-up

* tests: add globalTeardown

* tests: add afterall

* refacto(tests): add method createProject

* tests: remove registry deletion

* tests: remove maxWorkers

* tests: set maxWorkers=50%

* tests: change order of listProjects

* tests: maxWorkers=5

* tests: maxWorkers=6

* tests: run runtimes tests in parallel

* tests: parallelization for triggers and multi-regions

* fix(tests): fix deleteRegistryNamespace method

* tests: add catch in functions.test

* tests: add cleanup step in gha

* tests: update axios version

* tests: only test node20

* tests: change const to let

* tests: fix triggers

* tests: fix runtime tests

* fix: add process.chdir before serverless remove

* tests: fix runtimes/secrets

* ops: run suites in matrix

* tests: fix npm scripts for containers

* tests: use serverlessInvoke in runtime tests

* tests: clean up

* fix: run tests on branch master (and not main)

* tests: remove it import

* tests: remove maxConcurrency argument

* tests: fix trigger tests

* test: remove chai library in tests

* ops: add dependabot and linter

---------

Co-authored-by: Reda Noureddine <[email protected]>

Author: Bemilie

.eslintrc.js

@@ -1,17 +1,7 @@
 module.exports = {
-  "extends": "airbnb-base",
-  "plugins": ["import"],
-  "rules": {
-    "func-names": "off",
-
-    // support for node v4
-    "strict": "off",
-    "prefer-rest-params": "off",
-    "react/require-extension" : "off",
-    "import/no-extraneous-dependencies" : "off",
-    "prefer-destructuring": "off"
+  root: true,
+  extends: ["@serverless/eslint-config"],
+  rules: {
+    "import/prefer-default-export": "off",
   },
-  "env": {
-    "jest": true
-  }
-};
+};

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when
+an individual is representing the project or its community in public spaces.
+Examples of representing a project or community include using an official
+project e-mail address, posting via an official social media account, or acting
+as an appointed representative at an online or offline event. Representation of
+a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at opensource@scaleway.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq