Building upon the navigation to vale rules from pablomxnl/vale-cli-plugin!54, I would like to add navigation options that allow to navigate to styles directly from the .vale.ini files aswell: * If you ctrl + click on a style, you navigate to the style folder (the Readme.md or just the folder, if no Readme.md is present) * If the style folder does not exist, a notification is shown. For autocompletion, we scout the same directories where we would look for navigation targets for available styles and if the user presses cmd/ctrl+space, we calculate autocompletions if the cursor is currently editing the values of a "BasedOnStyles" entry in the .vale.ini file. I thought about whether to integrate the creation of new styles if they do not exist or even marking non-existent styles as errors in the .vale.ini at this point but implementation-wise this is an entirely different topic. Follow-up topics could be: * Validation of .vale.ini files (using the vale command line binary) * File templates for creating new rules and new .vale.ini files. This is similar to "new class" in java - a template that has some basic structure for you to directly dive into editing (this is the point where we could think about asking the user to create a Rule when navigating to a target from the vale.ini file that does not exist)