fix(pack): update typescript-all-in-one disable typescript-tools to denols

[JamsMendez]

📑 Description

In the pack typescript-all-in-one disable typescript-tools and tsserver to denols. Apparently tsserver is disabled but typescript-tools keeps tsserver errors active again.

ℹ Additional Information

[github-actions]

Review Checklist

Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:

Proper conventional commit scoping:

• If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin

• If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error

• Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above

• README is properly formatted and uses fenced in links with <url> unless they are inside a [title](url)

• Proper usage of opts table rather than setting things up with the config function.

[Uzaaft]

@JamsMendez Can you explain better what this PR does? Your original message didn't make much sense for me.

[JamsMendez]

@JamsMendez Can you explain better what this PR does? Your original message didn't make much sense for me.

Sorry @Uzaaft, the context is the following:
add in community.lua
{ import = "astrocommunity.pack.typescript-all-in-one" }
And in the astrolsp.lua configure tsserver so that the root_dir for package.json and tsconfig.json.
But when I open a Deno project the tsserver shows the errors of "cannot find name Deno", "Cannot find module...", etc.
Although the pack disables lsp tsserver, this is caused by lsp typescript-tools. As shown in the previous image.
The PR in summary disables typescript-tools so that these error messages are not displayed and Deno is the main lsp.

[Uzaaft]

I'm going to wait on merging this one until I find time to test it properly.

[aslak01]

Can confirm this is an issue, I used this solution to solve: pmizio/typescript-tools.nvim#248

[mehalter]

Did a bit of cleanup and made the modifications user facing so they can choose to disable them! I'll go ahead and merge this and if something is broken we can have follow up PRs. Also snuck in some fixes across other stuff which isn't a huge deal haha not worth another PR

[mehalter]

Thanks for starting this @JamsMendez !