Add Translations for Teams and Svelte Frontend Support

[askdkc]

No description provided.

[what-the-diff]

PR Summary

• Changes to .gitignore: The .gitignore file has been updated to ignore a certain directory (/boost).
• Improvement to README.md: The project's readme file now includes more detailed instructions on certain operations, such as using the new Svelte command for translating text at runtime, and more information about the Svelte starter kit.
• Alterations to composer.json: We've reintroduced larastan/larastan as a dependency for project development purposes.
• Updates to BreezejpCommand.php: This crucial file now has a new command option for translating Svelte templates and an integrated logic to handle Svelte template translations by prompting the user when required.
• Introduction of InstallSvelteI18n.php: This is a new element of the system designed to assist with installing globalization features into the Svelte system, including methodologies for patching Svelte files with translated text.
• Creation of i18n.ts file in stubs/js/: This is a new file for handling translation keys in the Svelte environment.
• Additions to CommandTest.php: There's a new test to verify expected translations in Svelte are correctly documented in a specific JSON file.
• Introduction of LangSwitchTest.php: This is a new set of tests to validate that the language switching software integration is implemented correctly.
• Addition of SvelteI18nTest.php: A new test file for checking the localization and setup process specifically for Svelte has been added.
• Addition of Login.svelte and PasskeyItem.svelte: New Svelte components for the user login functionality and passkey management have been created.
• Implemented Middleware: Middleware included that can share the application name with response set by Inertia, a JavaScript library we're using.
• Creation of Additional Tests: More tests have been created to ensure correct template publication, translations, and that the breezejp --svelte command can function properly even when run multiple times.
• Cleanup Mechanisms: Functions are in place to clean up files and directories once tests have been run to ensure a clean state.