Update default theme name in make script to append the date

[kevinfodness]

Description

To ensure there are different textdomains between the plugin and the theme, we should append the current year to the name of the theme when suggesting a theme name in the make script.

Use Case

When a user uses the make script to bootstap a project, it should suggest a theme name with the current year appended. For example, given a project name of example-project, the plugin slug should default to example-project and the theme slug should default to example-project-2024.

[goodguyry]

How about setting the default plugin name to have a -plugin suffix and leaving the theme name as-is?

Rationale: Having worked in a theme with a -2016 suffix for a while, that year ends up being a drag. It's one thing to notice code that seems a little outdated; the theme itself announcing its age can really compound the effect.

[kevinfodness]

The rationale behind this is that the plugin should grow and evolve over time, but the theme is intended to represent a particular graphical treatment of the front-end, which is rooted in a point in time when those decisions were made. Particularly with block themes, which this framework was crated to use, what is in the theme ends up being very light - it's mostly styles and templates, not functionality (that belongs in the plugin). Since most of the PHP code work is being done in the plugin, it's better to have that be a short slug that identifies the site/client/platform in question (e.g., alley) rather than having plugin appended (e.g., alley-plugin). This separation of concerns also makes it easier to create a new theme when there is a redesign with an updated year slug.

[kevinfodness]

Closed via #117