feat: Array to Twig migration part 1

[k11kirky]

IMPORTANT: This is part 1 of a 2 part change. After this is merged, we rename the repo and env variables then merge part 2

TL;DR

Renamed the product from "Array" to "Twig" across the codebase, including configuration files, protocol handlers, and user-facing text.

What changed?

• Renamed all user-facing instances of "Array" to "Twig" in the UI, window titles, and documentation
• Updated configuration file paths from .array/ to .twig/ and array.json to twig.json
• Added support for both twig:// and legacy array:// protocol handlers for deep linking
• Implemented migration logic to automatically move existing .array directories to .twig
• Maintained backward compatibility with legacy paths and configuration files
• Updated environment variables (keeping ARRAY_ prefix for now with a note about future migration to TWIG_)
• Preserved app data paths for compatibility with existing installations

How to test?

1. Verify the app name appears as "Twig" in window titles and UI elements
2. Confirm both twig:// and array:// deep links work correctly
3. Test that existing workspaces in .array are properly migrated to .twig
4. Verify that both twig.json and legacy array.json configuration files are recognized
5. Check that environment variables are correctly set in workspace terminals

Why make this change?

This rename from "Array" to "Twig" represents a product rebranding decision. The implementation maintains backward compatibility with existing installations while establishing the new brand identity across the codebase. The migration logic ensures a smooth transition for existing users by automatically moving directories and supporting legacy configuration paths.

[k11kirky]

• feat: Array to Twig migration part 2 #535
• feat: Array to Twig migration part 1 #534 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.