Add ADR for renaming templates

[rocketnova]

Ticket

• Rename app or add multiple apps template-infra#569

Changes

What was added, updated, or removed in this PR.

• ADR for renaming application template directories

Context for reviewers

Testing instructions, background context, more in-depth details of the implementation, and anything else you'd like to call out or ask reviewers. Explain how the changes were verified.

See ADR.

Testing

Screenshots, GIF demos, code examples or output to help show the changes working as expected. ProTip: you can drag and drop or paste images into this textbox.

N/A

[coilysiren]

My mundane POV is that this feels like a good place to use flask-app rather than app-flask.

Besides that, I'm hard +1 on renaming away from just app, for all the reasons mentioned here

[rocketnova]

Thanks for the comment! I tend to follow "bigger-to-smaller" in most things (e.g. YYYY-MM-DD) so that things naturally sort, which is how we ended up with template-application-flask, but I don't feel super strongly about it. Curious to see what other people think.

[haiyansui]

I didn't have an opinion but Rocket's explanation makes sense to me.

[sawyerh]

I like the idea of naming the app something that is easier to find-and-replace

[coilysiren]

👍!

[lorenyu]

At a high level seems like a reasonable direction, but I'm having difficulty evaluating without seeing the impact on:

• Setup process for integrating apps and infra (right now infra assumes apps are named app, so there needs to be an additional step that updates the infra template to get them to work)
• Update process for updating the templates (both app and infra)
• Impact on template development workflows, in particular (a) template CD which uses update process and (b) dev workflow which often relies on generating a patch from changes in a branch on platform-test and applying them to a branch on template-infra.

[aligg]

Read this over in detail and makes sense to me, like the idea of avoiding app/app in next.js