fix: add discord chat link for component testing readme (#8780)

Co-authored-by: Barthélémy Ledoux <ledouxb@me.com>

.github/ISSUE_TEMPLATE/component-testing.md

@@ -10,6 +10,8 @@ assignees: JessicaSachs
 <!-- 👋 Hello! --> 
 <!-- Cypress Component Testing is still in Alpha, so your feature requests and bug reports will help shape the future of the library. -->
 
+<!-- We're growing the Cypress Community Discord. We have dedicated sections on Component Testing. Join now and let's chat! 👉 https://discord.com/invite/TmzTGUW -->
+
 ### Summary
 <!-- Summarize the issue or feature request. -->
 <!-- This is also where you add additional context for the bug or feature, such as what the issue prevents you from achieving or what the proposed feature may enable to you accomplish -->

npm/vue/README.md

@@ -6,6 +6,8 @@
 [![renovate-app badge][renovate-badge]][renovate-app]
 
 > Browser-based Component Testing for Vue.js with the Open-Source [Cypress.io](https://www.cypress.io/) Test Runner ✌️🌲
+>
+**✨ New** We're growing the Cypress Community Discord. We have dedicated sections on Component Testing. 👉 [Join now](https://discord.com/invite/TmzTGUW) and let's chat!
 
 **Jump to:** [Comparison](#comparison), [Blog posts](#blog-posts), Examples: [basic](#basic-examples), [advanced](#advanced-examples), [full](#full-examples), [external](#external-examples), [Code coverage](#code-coverage), [Development](#development)
 
@@ -653,6 +655,10 @@ If you want to disable code coverage instrumentation and reporting, use `--env c
 
 **Note ⚠️:** if the component `.vue` file does not have a `<script>` section, it will not have any code coverage information.
 
+## What happened to cypress-vue-unit-test?
+
+We were in the middle of moving into the Cypress NPM org, so any references to `cypress-vue-unit-test` should be switched to `@cypress/vue`. Once complete, the old repository will be archived.
+
 <a name="#development"/>
 
 ## Development