refactor(api): ♻️ consolidate delimited string parsing into reusable extension

[Copilot]

Environment variables and multi-input arguments (VOID_PLUGINS, VOID_NUGET_REPOSITORIES, etc.) were parsed with inconsistent delimiter handling—some using simple Split(',', ';'), others using regex for escaped delimiters.

Changes

• Added StringExtensions.SplitByDelimiters() in src/Api/Extensions/

  • Default delimiters: ,, ;, \n
  • Optional escape character support (e.g., \; for literal semicolons)
  • Compiled regex for escaped delimiter performance
  • Auto-trims and removes empty entries by default

• Refactored PluginService.cs

  - return args.Split(',', ';');
  + return args.SplitByDelimiters();

• Refactored NuGetDependencyResolver.cs

  - UnescapedSemicolonRegex().Split(env ?? "").Select(repo => repo.Replace(@"\;", ";"))
  + (env ?? "").SplitByDelimiters([';'], escapeCharacter: '\\')

  • Removed UnescapedSemicolonRegex() partial method
  • Removed partial keyword from class

• Added 16 unit tests covering default/custom delimiters, escape handling, trimming, and real-world scenarios

Example Usage

// Simple case (default delimiters: , ; \n)
"a,b;c".SplitByDelimiters()  // ["a", "b", "c"]

// With escaped delimiters
@"url1\;extra;url2".SplitByDelimiters([';'], escapeCharacter: '\\')  // ["url1;extra", "url2"]

Original prompt

VOID_PLUGINS
VOID_NUGET_REPOSITORIES

These env vars and may be some other code like for parsing program arguments are using multi inputs that are split with delimiters like ';' or any another.

I'd like you to find all places in code where this logic applies and dedicate that logic into same place so all places reuse it same way. Maybe just extension method that splits the string by delimiters. Default delimiters should include ,; and \n or \r\n

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.