fix: moved vuelidate utils from es-ds-docs to es-ds-components so EsZipCodeForm won't break

[ericdouglaspratt]

🔗 Linked issue

• https://energysage.atlassian.net/browse/CED-1900

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

• EsZipCodeForm uses consts like vuelidateKeys and vuelidateMaxLength - these consts are not defined in es-ds-components, so I was getting downstream errors of "vuelidateKeys is undefined" when trying to use EsZipCodeForm
• I found these consts defined in utils files in es-ds-docs, which is why VS Code thought they were available even though they weren't. I've moved them into es-ds-components so they'll be exported along with EsZipCodeForm

🥼 Testing

• Tested locally on es-cms-pages homepage with PageCtaBannerV2

🧐 Feedback Requested / Focus Areas

• Overall

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.
• I have documented testing approach

[swarmia]

✅  Linked to Task CED-1900 · Upgrade homepage to Nuxt 3 in es-cms-pages
➡️  Part of Epic CED-1443 · Upgrade CMS micro frontends to Nuxt 3 [LC]

[lgeggleston]

Makes sense!