Put unbundled edges in a separate key in the control point table

[maxkfranz]

Cross-references to related issues. If there is no existing issue that describes your bug or feature request, then create an issue before making your pull request.

Associated issues:

• Edge points not calculated properly for bundled beziers when an unbundled edge exists between the same source and target #3322
• Repeated renderings of edges and O(n²) complexity when rendering multiple Bezier edges #3309

Notes re. the content of the pull request. Give context to reviewers or serve as a general record of the changes made. Add a screenshot or video to demonstrate your new feature, if possible.

• Fixes the issue specified in Edge points not calculated properly for bundled beziers when an unbundled edge exists between the same source and target #3322.
• Cleans up the debug page so it's easier to see. It looks like it got complicated over several previous PRs.
• The fix is to just use a different key in the table for unbundled edges.

Debug page before:

Debug page after:

You can see in the debug page (npm run watch) that the parallel edges in f34682c are incorrect without the fix, and they are correct with the fix in a16b04e.

Parallel edges without the fix. Note that the beziers are incorrect with the unbundled, bent edge in there:

Checklist

Author:

• The proper base branch has been selected. New features go on unstable. Bug-fix patches can go on either unstable or master.
• Automated tests have been included in this pull request, if possible, for the new feature(s) or bug fix. Check this box if tests are not pragmatically possible (e.g. rendering features could include screenshots or videos instead of automated tests).
• The associated GitHub issues are included (above).
• Notes have been included (above).
• For new or updated API, the index.d.ts Typescript definition file has been appropriately updated.

Reviewers:

• All automated checks are passing (green check next to latest commit).
• At least one reviewer has signed off on the pull request.
• For bug fixes: Just after this pull request is merged, it should be applied to both the master branch and the unstable branch. Normally, this just requires cherry-picking the corresponding merge commit from master to unstable -- or vice versa.