Show warning for old entity spec version

[ktuite]

Frontend of getodk/central-backend#1272

Issue getodk/central#730

What has been done to verify that this works as intended?

Why is this the best possible solution? Were any other approaches considered?

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

Does this change require updates to user documentation? If so, please file an issue here and include the link below.

Before submitting this PR, please make sure you have:

• run npm run test and npm run lint and confirmed all checks still pass OR confirm CircleCI build passes
• verified that any code or assets from external sources are properly credited in comments or that everything is internally sourced

[matthew-white]

I think this predated your changes, but I feel like we're trying to impose a structure on these warnings that doesn't necessarily exist. We have three warnings, and we render each differently. Instead of trying to use computed properties and methods, could we use v-if/v-else? I think that'd be clearer overall. I'm thinking of something like:

<template v-if="warning.type === 'deletedFormExists'">
  {{ $t('warningsText[3].deletedFormExists, { value: warning.details.xmlFormId }) }}
  <doc-link to="central-forms/#deleting-a-form">{{ $t('moreInfo.learnMore') }}</doc-link>
</template>
<template v-else-if="warning.type === 'structureChanged'">
  {{ $t('warningsText[3].structuredChanged') }}
  <doc-link to="central-forms/#central-forms-updates">{{ $t('moreInfo.learnMore') }}</doc-link>
  <span>
    <br>
    <strong>{{ $t('fields') }}</strong> {{ warning.details.join(', ') }}
  </span>
</template>
<template v-else-if="warning.type === 'oldEntityVersion'">
  {{ $t('warningsText[3].oldEntityVersion, { value: warning.details.version }) }}
  <a href="https://getodk.github.io/xforms-spec/entities" target="_blank">{{ $t('moreInfo.learnMore') }}</a>
</template>

For example, I think it's easier to see here that while each warning shows an i18n message, they all work a little differently. deletedFormExists shows details.xmlFormId, oldEntityVersion shows details.version, and structureChanged only shows static text. Its details is actually an array of fields, which are shown in a separate <span>.

[ktuite]

I like this a lot better, I was struggling with how to manage these different, yet in some ways similar, cases.

[matthew-white]

I think curly quotes are usually a nice touch:

Suggested change

	"oldEntityVersion": "Entities specification version \"{value}\" is not compatible with Offline Entities. Please use version 2024.1.0 or later."
	"oldEntityVersion": "Entities specification version “{value}” is not compatible with Offline Entities. Please use version 2024.1.0 or later."

[ktuite]

Should I change it for the deletedFormExists string above, too, or would that require it to get re-translated (so maybe I should just leave it as is)?

[matthew-white]

Yeah, I think it's not worth it getting re-translated. It'll be nice to have curly quotes in the new warning though.

[ktuite]

could call value version in the translation message

[ktuite]

Could possibly say "We recommend using version 2024.1.0 or later..." to leave it more open ended?