Problem:  not all nushell files detected
Solution: use *.nu to detect nushell files

closes: vim/vim#13586

https://github.com/vim/vim/commit/b9efc72c2432f2d2a633c12d3a5b9fc3efb7b6e7

Co-authored-by: Daniel Buch Hansen <boogiewasthere@gmail.com>

Add syntax and filetype plugins for SWIG (Simplified Wrapper Interface
Generator) description files.

The default syntax for .i files highlights comments in a reverse
color scheme which doesn't look well.  This syntax builds
on vim's c++ syntax by adding highlighting for common swig
directives and user defined directives.  For an alternative
syntax, see vimscript vim/vim#1247 (which I found after writing this).

closes: vim/vim#13562

https://github.com/vim/vim/commit/2e31065a650015892179e520038bf2083a9519b6

Co-authored-by: Julien Marrec <julien.marrec@gmail.com>
Co-authored-by: Matěj Cepl <mcepl@cepl.eu>

Problem:  wast filetype should be replaced by wat filetype
Solution: start using the official wat filetype name

runtime: rename `wast` filetype to `wat` (Wasm text format)

The problem is the name of the current filetype wast. When the plugin
was initially created, the file extension for Wasm text format was not
fixed and .wast was more popular.

However, recently .wat became the official file extension for
WebAssembly text (WAT) format and .wast is now a file extension for the
unofficial WAST format, which is a superset of .wat for the convenience
to describe the Wasm specification conformance tests.

https://webassembly.js.org/docs/contrib-wat-vs-wast.html

However for now, let's keep using the `wat` filetype even for the .wast
extension, so that we at least do not lose the filetype settings and
syntax highlighting. This can be adjusted later, if it turns out to have
a separate need for.

closes: vim/vim#13533

https://github.com/vim/vim/commit/bc8f79d36a456054ed29f46585830af6d71f57c8

Co-authored-by: rhysd <lin90162@yahoo.co.jp>

Problem:  No filetype support for xcompose files
Solution: Add filetype detection

closes: vim/vim#13508

https://github.com/vim/vim/commit/4f9074b96cc7efb1c829ca74902a851551dcf4e8

Problem:  No support for cypher files
Solution: Add cypher filetype detection

Cypher query language support to work with (mostly) graph databases.

Already existing lsp support in Neovim's nvim-lspconfig:
https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#cypher_ls

closes: vim/vim#13516

https://github.com/vim/vim/commit/8f0fe20ff1a13b468fdfaf85c434475f75c7a615

Co-authored-by: Gerrit Meier <meistermeier@gmail.com>

Problem:  objdump files not recognized
Solution: detect *.objdump files, add a filetype plugin

Added the objdump file/text format

closes: vim/vim#13425

https://github.com/vim/vim/commit/10407df7a95d0311c7d2eb920d3b72020db5b301

Co-authored-by: Colin Kennedy <colinvfx@gmail.com>

Problem:  pacman hooks are detected as conf filetype
Solution: make it consistent to pacman.conf and detect those
          hooks as confini

Because confini has much better syntax highlighting than conf.

For reference, I identified pacman.conf and pacman hooks as dosini in
https://github.com/vim/vim/pull/6335, then
https://github.com/vim/vim/pull/10213 changed them to conf, then
https://github.com/vim/vim/pull/10518 changed pacman.conf to confini but
forgot to change hooks.

closes: vim/vim#13399

https://github.com/vim/vim/commit/7d254dbc2db35badc65668db85f826f605486986

Co-authored-by: Guido Cella <guido@guidocella.xyz>

Problem:  Janet files are not recognised
Solution: Add filename and shebang detection (without
          adding an extra filetype plugin)

Those are used by the Janet language:
http://www.janet-lang.org

closes: vim/vim#13400

https://github.com/vim/vim/commit/c038427d2a27445e612761f19c92b2b8b05afdea

Co-authored-by: Doug Kearns <dougkearns@gmail.com>

Problem:  not able to detect xkb filetypes
Solution: Detect files below /u/s/X11/xkb as xkb files (without adding
          an extra filetype)

Those files are used from the X11 xkb extension

closes: vim/vim#13401

https://github.com/vim/vim/commit/ae9021a840db3253b0e0cb84186faae73368afd7

Co-authored-by: Guido Cella <guido@guidocella.xyz>

Problem:  *.{gn,gni} files are not recognized
Solution: Detect some as gn filetype (without adding an extra filetype)

Those come from: https://gn.googlesource.com/gn/

closes: vim/vim#13405

https://github.com/vim/vim/commit/84394f2be4a750f1e26b478e36de041663f4b5a4

Co-authored-by: Amaan Qureshi <amaanq12@gmail.com>