Update feature issue template to check if audit event is required

What does this MR do and why?

With a unified approach in defining audit events so that they are maintainable and sustainable as audit events, we want to also ensure that audit events are thought about during the planning and development of new features. This is so developers do not need to go back to add audit events after a feature has been released.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Closes #393303 (closed)