Add brief clarification on scenario compatibility

[thomas-qah]

What?

This PR adds a brief line explaining what it means if the scenario version is different from the current model version.

Why?

To make the user aware of the possible implications of older scenario versions.

How?

See changes.

Closes #4145

[mabijkerk]

Two points of feedback:

1. The Dutch translation seems to be missing
2. I'm not sure this solves Update text on compatibility when viewing scenario description #4145, as I see it, this PR only adds a more extensive explanation. What the issue describes is that users do not know if their scenario is being kept up to date or not. I feel the goal of the issue would be to make clear to the user if keep_compatible is set to true or false. Do you agree @noracato?

To expand on 2. I think that the we have the following options, that we want to clarify to our users:

• Keep_compatible is set to false and there has been a Deploy: the scenario is not changed, but there is a risk that it is broken
• Keep_compatible is set to true and there has been a Deploy: the scenario may be changed, but there is no risk that it is borken

[github-actions]

This pull request has had no activity for 60 days and will be closed in 7 days. Removing the "Stale" label or posting a comment will prevent it from being closed automatically. You can also add the "Pinned" label to ensure it isn't marked as stale in the future.

[github-actions]

This pull request has had no activity for 60 days and will be closed in 7 days. Removing the "Stale" label or posting a comment will prevent it from being closed automatically. You can also add the "Pinned" label to ensure it isn't marked as stale in the future.