Refactor Saas naming, structure and modules

- Add more documentation.
- Use `main.scss` instead of importing components individually. This
  improves productivity without compilation errors due to missing
  imports and allows for easier future file/folder changes and
  refactorings inside `./styles`.
- Use partials with underscored naming. Because it documents that the
  files should not be individually imported.
- Introduce `third-party-extensions` folder to group styles that
  overwrites third party components.
- Refactor variable names from generic to specific.
- Use Sass modules (`@use` and `@forward`) over depreciated `@import`
  syntax.
- Separate font assets from Sass files (`styles/`). Create `assets/`
  folder that will contain both.
- Create `_globals.css` for global styling of common element instead of
  using `App.vue`.

src/presentation/components/Scripts/View/TheScriptsView.vue

@@ -95,15 +95,13 @@ export default class TheScriptsView extends StatefulVue {
 </script>
 
 <style scoped lang="scss">
-@import "@/presentation/styles/colors.scss";
-@import "@/presentation/styles/fonts.scss";
-@import "@/presentation/styles/media.scss";
+@use "@/presentation/assets/styles/main" as *;
 
-$inner-margin: 4px;
+$margin-inner: 4px;
 
 .scripts {
-    margin-top: $inner-margin;
-    @media screen and (min-width: $vertical-view-breakpoint) { // so the current code is always visible
+    margin-top: $margin-inner;
+    @media screen and (min-width: $media-vertical-view-breakpoint) { // so the current code is always visible
         overflow: auto;
         max-height: 70vh;
     }