[C#] Add regex to argument strings in known functions (#4522)

Co-authored-by: Keith Hall <kingkeith+github@gmail.com>
Co-authored-by: deathaxe <16542113+deathaxe@users.noreply.github.com>

[C#] Add regex to argument strings in known functions (#4522)

Co-authored-by: Keith Hall <kingkeith+github@gmail.com>
Co-authored-by: deathaxe <16542113+deathaxe@users.noreply.github.com>

[D, Makefile, Rust] Standardize build output scopes (#4365)

* [D] Standardize build output scopes

* [Makefile] Standardize build output scopes

* [Rust] Standardize build output scopes

* Change base scope to text.build-output

* Tweak scope for result line

[D, Makefile, Rust] Standardize build output scopes (#4365)

* [D] Standardize build output scopes

* [Makefile] Standardize build output scopes

* [Rust] Standardize build output scopes

* Change base scope to text.build-output

* Tweak scope for result line

[HTML] Improve conflict markers in tags and values (#4238)

* [HTML] Move syntax tests to tests/ directory

* [HTML] Fix various conflict marker issues

This commit explicitly includes `merge-conflict-markers` in front of
each tag end punctuation (`>` or `/>`) to ensure conflict markers
taking precedence.

Including that context in `tag-attributes` is not sufficient as it is
included after tag end punctuation patterns.

Including that context in `prototype` is not sufficient as as it is
excluded from tag attribute contexts for templating languages to inject
template tags only within attribute names or values using `prototype`.

Syntax tests are reorganized in a dedicated test file.

[HTML] Improve conflict markers in tags and values (#4238)

* [HTML] Move syntax tests to tests/ directory

* [HTML] Fix various conflict marker issues

This commit explicitly includes `merge-conflict-markers` in front of
each tag end punctuation (`>` or `/>`) to ensure conflict markers
taking precedence.

Including that context in `tag-attributes` is not sufficient as it is
included after tag end punctuation patterns.

Including that context in `prototype` is not sufficient as as it is
excluded from tag attribute contexts for templating languages to inject
template tags only within attribute names or values using `prototype`.

Syntax tests are reorganized in a dedicated test file.

Add "interactive" option for build systems

Add "interactive" option for build systems

[Diff] Refactor for Diff3, Git, and conflicts (#4111)

[Diff] Refactor Diff, Git Diff and Diff3

This commit...

1. rewrites Diff and Diff3 syntax according to the GNU and SVN documentation.
2. adds new Git Diff syntax, also used by Git Log.

## Notable changes

- new support for
    - Diff3 formats
    - Conflict sections
    - "Combined" unified diffs, only in Git Diff
- new syntax for Git Diff emails (`git am` and `git format-patch`)
  - if normal Diff syntax detects the "magic" first line, 
    it delegates out to Git Diff instead.
- tweaked scopes, preserving stacking from #2178 for backwards-compatibility
- lots of documentation links
- lots of new tests, mostly pulled from relevant documentation

Co-authored-by: deathaxe <deathaxe82@googlemail.com>

[Diff] Refactor for Diff3, Git, and conflicts (#4111)

[Diff] Refactor Diff, Git Diff and Diff3

This commit...

1. rewrites Diff and Diff3 syntax according to the GNU and SVN documentation.
2. adds new Git Diff syntax, also used by Git Log.

## Notable changes

- new support for
    - Diff3 formats
    - Conflict sections
    - "Combined" unified diffs, only in Git Diff
- new syntax for Git Diff emails (`git am` and `git format-patch`)
  - if normal Diff syntax detects the "magic" first line, 
    it delegates out to Git Diff instead.
- tweaked scopes, preserving stacking from #2178 for backwards-compatibility
- lots of documentation links
- lots of new tests, mostly pulled from relevant documentation

Co-authored-by: deathaxe <deathaxe82@googlemail.com>