Refactor description of arrays in debugger.

[sampottinger]

Closes #606, builds on #692 from @WillRabalais04.

[sampottinger]

[edited slightly]

Hey @WillRabalais04! Can you do a code review on this and see how my additions feel? It’s built from your #692 (thank you! 👍✨) with a few additions:

• The function was getting a bit nested so broke out a private method for the array case.
• I like what you did with the regex but, as I was working with it, I noticed all of your logic could all fit into your regex itself, saving us a branch on if multi-dimensional array.
• Added tests (use ant test)!

Re, regex: We can reverse out on this. Curious to get your opinion. Given the age and multiple strata from multiple generations of contributors (😅) I've found that, for Processing, sometimes consolidating to a documented / tested regex is sometimes a bit easier to maintain when working on some of the string manipulation if the regex isn’t too involved.

[sampottinger]

CC @SableRaf - Is it possible to add GSoC folks to the repo if they join our communal pledge not to push direct to main? @WillRabalais04 - how would you feel about that power / responsibility?

[SableRaf]

CC @SableRaf - Is it possible to add GSoC folks to the repo if they join our communal pledge not to push direct to main?

We could also consider adding branch protection to the repository: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches

[sampottinger]

Yeah I’m into that. I think we haven’t so far because the list of contributors with upstream access has been small. Requiring pr (with an exceptions list including Ben) to get to main would be ideal either way though.

[sampottinger]

Superseded by #729