refactor(typescript)!: remove eslint and prettier

[azdanov]

Closes #1501

📑 Description

This should be done after #1502 and #1503. I merged dap.lua, since now the init.lua file is smaller and more managable.
I noticed that yioneko/nvim-vtsls is used, but I'm not sure if it was configured properly or not to use custom commands. Maybe those needs to be assigned to some keys.

Need to check if there are any other packs (angular/vue, etc) depend on this one.

• astrocommunity/lua/astrocommunity/pack/angular/init.lua

  Line 2 in b69674d

  { import = "astrocommunity.pack.typescript" },

• astrocommunity/lua/astrocommunity/pack/svelte/init.lua

  Line 2 in b69674d

  { import = "astrocommunity.pack.typescript" },

• astrocommunity/lua/astrocommunity/pack/vue/init.lua

  Line 2 in b69674d

  { import = "astrocommunity.pack.typescript" },

• astrocommunity/lua/astrocommunity/pack/astro/init.lua

  Line 2 in b69674d

  { import = "astrocommunity.pack.typescript" },

ℹ Additional Information

See previous issue #962 where discussion was about adding biome.js, maybe there are some relevant details there.

[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)

• Entry returns a single plugin spec with the new plugin as the only top level spec (not applicable for recipes or packs).

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

• Proper usage of specs table for all specs that are not dependencies of a given plugin (not applicable for recipes or packs).