docs rewrite working conventions

[Ryun1]

List of changes

• Changed documentation to improve intended working conventions

Checklist

• related issue
• My changes generate no new warnings
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the changelog
• [] I have added tests that prove my fix is effective or that my feature works

[Ryun1]

While we are here, is there any nice-to-haves/tech debt that people would prefer?
like switching everything to yarn instead of npm

[MSzalowski]

While we are here, is there any nice-to-haves/tech debt that people would prefer? like switching everything to yarn instead of npm

+1 for switching to yarn 💪

Regarding tech debt - we had a meeting with frontend guys and they pointed out:

1. I18n integration - to avoid strings that are in many places duplicated (and gradually migrate them to some kind of application content storage).
2. Unification of consts (currently application have checks of types to string eg. https://github.com/IntersectMBO/govtool/blob/f66591ab7156fe80996f5addf2de8356463365f3/src/vva-fe/src/context/wallet.tsx#L337C18-L337C18).
3. Inline styles and duplicate components if there are any (needs investigation).
4. Eslint, tsc, husky to have the unified code style and checks on commit.
5. Wallet refactor - 1.2k of lines seems to be impossible to refactor at once but as it is one of the most crucial parts of the application I think that we should take care of designing the architecture for that module and again - gradually improve that file to increase the readability and maintainability.

Also - @JanJaroszczak provided PR with initial unit tests that are also a good starting point for any other unit tests that might be added to github actions.

What do you think?