Adding deno.config

[otherJL0]

Adding a deno.config file provides:

• A recognizable file for the deno lsp to reference when working in editors other than VSCode
• A set of tasks to build and test with all flags with deno task build and deno task test

At this time the "fmt" section of the config is set to ignore all files since the current style deviates from deno's default style.

[what-the-diff]

• .gitignore
• vscode settings
• README markdownlint configs and deno tasks added to the readme file
• new jsonc configuration for deno compiler options, import map, fmt and task scripts (deno run)
• removed tsconfig since it is not needed anymore with a jsonc configuration in place

[mxcl]

Do we still need tsconfig.json?

[mxcl]

We should probably change the tea scripts in our README to use deno build and deno test. Edit or however you call these “tasks”, since I haven't read the docs.

[otherJL0]

We don't really need tsconfig.json anymore, I can remove it and update the PR. And yeah we could update the README with the new task commands.

[lino-levan]

Any particular reason why this is a .json and not a .jsonc? I don't think it matters yet but if we ever want to add comments to it I think it would be valuable to have.

[jhheider]

At this time the "fmt" section of the config is set to ignore all files since the current style deviates from deno's default style.

A better question is: "should we codify our deviations and enable formatting?"

[mxcl]

A better question is: "should we codify our deviations and enable formatting?"

probs, though necessary for this PR!

[otherJL0]

deno-config.json is now deno-config.jsonc to allow for future comments. The README has been updated to use the more succinct deno task syntax for local development