Testing template's strategy

Is it worth it to test all new contributions?

We don’t have a way to ensure the sample will keep working, right? It can be broken at any time in the future.

I think we should re-think and reflect on what we can do on awesome-azd to help customers to know if a template works or not. I have some ideas on my mind, but, what do you think? The general problem/situation is:

- As awesome-azd maintainers:
o we don’t want to publish a new template w/o testing it at least one time (the first time only).
o After the template is merged, we don’t have a way to track/check if the template is broken at any point.

- As awesome-azd users:
o I don’t know if a template is currently broken or not. I can only try to run it myself and if it doesn't work, seek for help on the template’s owner.

- As template owner
o I am not obligated to add CI/CD for my template to publish it to awesome-azd.
o I don’t know if something changes in the future and my template breaks.

So, questions:
- Do we want to design something to help maintainers, users and owners to:
o Know if a template works before trying it.
o Know the last time when a template was used/tested.
o Tell/Notify owners if a template breaks.