Enhance issue reporting template with version validation

[MilanKovacic]

This PR introduces a validation step in the issue reporting template to ensure that issues are reported against the latest version of the extension. The rationale behind this change is to streamline the issue resolution process by focusing efforts on current problems, reducing the time spent on issues already addressed in recent updates, and encouraging users to keep their installations updated.

[sheremet-va]

Do we need the version input now? We also ask for output content which includes the version anyway.

[ffMathy]

The version output, doesn't that only include the Vitest packages? This would be for the version of the extension itself.

[ffMathy]

The version output, doesn't that only include the Vitest packages? This would be for the version of the extension itself.

[sheremet-va]

The version output, doesn't that only include the Vitest packages? This would be for the version of the extension itself.

Please, look at the current issue template. It has "Output" (logs from the "Output" window) and "Version" fields. If we include the check from this PR, then why do we need the "Version" field?

[MilanKovacic]

The primary reason for keeping the version field, even with the required version validation step, is to ensure we can easily see the specific extension version that the issue was reported against.

Over time, the "latest version" information from the validation step may become less meaningful. The version field provides a clear, accessible record of the exact version used when the issue was reported. This is important if you are looking at the issue that is 2 weeks old, and now the "latest version" has changed from the time issue was opened.