Feature: Update Readme to help developers handle prettier errors. (#1529)

* Update Readme to help developers handle prettier errors in the Config UI tests

* Minor improvements in README for prettier trouble shooting

Co-authored-by: Priebe Daniel <dpr@novatec-gmbh.de>
Co-authored-by: Heiko Holz <heiko.holz@novatec-gmbh.de>

Author: 3 people

components/inspectit-ocelot-configurationserver-ui/README.md

@@ -33,6 +33,19 @@ And the following to fix them automatically.
 yarn lint:fix
 ```
 
+### Prettier
+
+When facing prettier/prettier errors in the Config UI tests and developing with VS Code, follows these steps for problem solving:
+
+* make sure to install the [prettier extension from Prettier](https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode)
+* open the file in which the prettier errors occur 
+* format the document using prettier
+  1. to format the document, open the command palette with `Ctrl + Shift + P` (Windows) or `Cmd + Shift + P` (Mac) 
+  2. search for `Format Document With...`. 
+  3. press Enter
+  4. in the opened drop down menu you can choose your preferred code styling (in this case prettier). Select `prettier` and press Enter
+* the opened code file will automatically be formatted by prettier, which will fix the prettier errors in the Config UI tests.
+
 #### Storybook
 
 The project also contains [Storybook](https://storybook.js.org/) which supports the development of components by providing an isolated sandbox UI for testing these components.