Safety for system running parallel threads of Prettier

[Janther]

In this comment I was made aware that prettier can be run asynchronously.

When parsing, we recollect data from our AST tree, that if run in parallel jobs, will generate errors in formatting.

Right now our parsing is not async so there shouldn't be any issue. but if at any point slang or prettier decide that their API should be asynchronous, we must address this.

This solution changes the signature of the constructor of nodes, making it necessary the passing of Prettier's options object which is unique per job.

The important changes happen in src/slang-nodes/SlangNode.ts (where we collect the data), src/slangSolidityParser.ts (where we used to clear the data for the next run), and src/types.d.ts (where we define the type that will contain the data). Everywhere else the changes are just to modify the constructor signature and initiate each new node with the options object.

I didn't want to complicate the signatures of the nodes' constructor and already half of the nodes receive the Prettier options object. Using an _prettier_solidity_ to prepend the names of the attributes seemed like a good enough solution but I'm willing to revisit this if we decide is safer in another way.