Should the template setup localizations?

Should the template include the necessary work to set up localizations? This includes adding an l10n.yaml, en.arb, modify the pubspec.yaml to generate localization, and use the AppLocalizations for Strings throughout the app.

This might be overkill for intermediate developers or it might be a healthy nudge in the right direction. What are your thoughts?

1. No localizations
2. Placeholder that links to more information
2. Localize only the title of the app
3. All strings localized

Background: https://flutter.dev/docs/development/accessibility-and-localization/internationalization

Review the referenced Flutter internationalization guidance and the named l10n.yaml, en.arb, and pubspec.yaml setup points. Decide which localization scope the template should support, then verify that the chosen scope is reflected in the app's strings and AppLocalizations usage.

Written by the indexing model from the issue text.