Upgrade Vue from 3.2.23 to to 3.2.31

Vue 3.2.25 and above reintroduce a Vue 2 feature that had been
temporarily removed in Vue 3, so staying on a Vue 3 version before
3.2.25 causes unnecessary compatibility problems. (The behavior change
in question isn’t well documented – see [1] – but seems to be related to
the behavior of refs inside v-for.)

(Note that we’re still on the compatibility build, this commit isn’t
changing that yet.)

[1]: vuejs/v3-migration-guide#10

Bug: T304717
Change-Id: I9b517b66edc6356079c49cb3ece0373c8284c2d3

Author: lucaswerkmeister

RELEASE-NOTES-1.39

@@ -40,6 +40,7 @@ For notes on 1.38.x and older releases, see HISTORY.
 * …
 
 === External library changes in 1.39 ===
+* Vue/compat updated from 3.2.23 to 3.2.31
 * …
 
 ==== New external libraries ====

resources/lib/foreign-resources.yaml

@@ -351,9 +351,9 @@ sinonjs:
 
 vue:
   type: tar
-  # This is the migration build of Vue 3.2.23 which provides compatibility for Vue 2 code
-  src: https://registry.npmjs.org/@vue/compat/-/compat-3.2.23.tgz
-  integrity: sha512-ap/aO8V1j3dveHGcELRQZdb3dlnMgCK5N5Ur6Q37RRtMcB1glJldqUP46aAhY7kMberaUVWwYehMothocsF6Dg==
+  # This is the migration build of Vue 3.2.31 which provides compatibility for Vue 2 code
+  src: https://registry.npmjs.org/@vue/compat/-/compat-3.2.31.tgz
+  integrity: sha512-hhwJk/SRwpT2OADctj+t7QZCRIgh04AcelGpe6gdj0OxA75xpHnPrG+fmG37U3Z6WDrNHZpGvu2eXBzWXM4OVA==
   dest:
     package/README.md:
     package/LICENSE: