Improve dev environment

[nksazonov]

Development environment improvement

Motivation

Smart contract development environment has never been fully set in Yellow, and this have already caused some inconvenience in work process.

This issue aims at establishing dev env with the following properties:

• practical - every aspect of environment is used, nothing is present 'just because someone likes it'; only best-suit plugins are used
• logical - everything is organised in a reasonable way
• easy-to-use - each process requires no additional adjustments
• expandable - extending environment with some additional module must not require changing existing environment
• self-explanatory - usage of each file, script, task, etc. is either implicitly stated by its name or explicitly described in a concomitant file

Structure

Each improvement section is to be extracted and resolved as a separate issue in the order presented.

Improvements

Structure (see #13)

Change the structure of the project so that each file has a logical location and naming.

---

Plugins (see #14)

Add useful plugins, revise settings of existing ones and implement changes caused by those actions.

---

Packages (see #15)

Make sure the latest versions of packages are used, there is no unused packages and no vulnerabilities.

---

Relation to other Yellow departments (see #16)

Ensure other departments can easily access the information they need without SC team's help.

---

Tools (see #17)

Standartize external tools usage.

---

Gas benchmarks (see #18)

Introduce gas benchmarks to be able to optimise smart contracts easily.

---

CI/CD (see #19)

Introduce Continuous integration / Continuous development by adding GH actions or using other technologies.

---