🔧 Resolve toc patterns in intentional order

[fwkoch]

The new project tocs introduced support for pattern entries, where users may specify a glob pattern as part of their tree. However, these were just getting resolved to a flat list of files, ordered by default system ordering.

This PR adds much more explicit handling of patterns. glob is still used to collect the files, but then we:

• keep folder nesting
• order within each folder as: index, remaining files in alpha order, then subfolders in alpha ordrer
• deduplicate files in the tree, so if you specify a file that is also part of a pattern, it will not show up in the resolved pattern tree
• respect exclude from project frontmatter

These changes mean pattern resolution is similar to the implicit project resolution, with a few small differences:

• patterns do not automatically ignore files like _build, node_modules, .* - they can still be ignored with exclude
• index file is handled at a per-folder level (maybe we want this behavior for implicit resolution...?)
• deduplication of files is not required on implicit resolution since files are never encountered twice there.

This addresses #1244 - it also addresses #1243 in the process, since we resolve patterns to create a new tree without patterns.

[fwkoch]

Chatted through this with @rowanc1 - merging without official review.

This also fixes up the test failure that is currently plaguing all builds.