docs: Update docs about plugins and bump package dependencies

Author: tjtanjin

docs/api/events.md

@@ -12,7 +12,7 @@ This page documents all available `events` emitted by the chatbot that may be li
 - You are using [**plugins**](/docs/concepts/plugins) that relies on events emitted by the chatbot (you should refer to the plugin documentation for what events are needed)
 
 :::tip Tip
-Before adding your own listeners with custom logic for events, it may be helpful to lookup existing [**plugins**](/docs/concepts/plugins) in case there's already a solution out there (e.g. [**rcb-input-validator-plugin**](https://github.com/react-chatbotify-plugins/rcb-input-validator-plugin)).
+Before adding your own listeners with custom logic for events, it may be helpful to lookup existing [**plugins**](/docs/concepts/plugins) in case there's already a solution out there (e.g. [**input-validator**](https://github.com/react-chatbotify-plugins/input-validator) plugin).
 :::
 
 ## Overview

docs/concepts/conversations.md

@@ -178,7 +178,7 @@ For manipulating messages, it is recommended that you utilize `injectMessage` an
   </div>
 </div>
 
-Toasts are strictly speaking not essential for chatbot conversations. However, they are oftentime useful in providing feedback to users (as **outlined in red** on the image above). For example, the [**rcb-input-validator-plugin**](https://github.com/react-chatbotify-plugins/rcb-input-validator-plugin) uses toasts to inform users of any input validation errors. A toast comprises of **3 properties**:
+Toasts are strictly speaking not essential for chatbot conversations. However, they are oftentime useful in providing feedback to users (as **outlined in red** on the image above). For example, the [**input-validator**](https://github.com/react-chatbotify-plugins/input-validator) plugin uses toasts to inform users of any input validation errors. A toast comprises of **3 properties**:
 
 - id (required) - an auto-generated uuidv4 `string`, uniquely identifying a toast
 - content (required) - a `string` or `JSX.Element`, representing the content of the toast

docs/concepts/plugins.md

@@ -13,16 +13,18 @@ A newly added feature in **v2** of the chatbot, the `plugins` prop provides user
 
 There is a small group of official plugins maintained, which provide useful functionalities in common use cases. As of the last update, the list of official plugins are as below:
 
-- [**rcb-input-validator-plugin**](https://github.com/react-chatbotify-plugins/rcb-input-validator-plugin) [Work-In-Progress]
-- [**rcb-message-transformer-plugin**](https://github.com/react-chatbotify-plugins/rcb-message-transformer-plugin) [Work-In-Progress]
+- [**Input Validator**](https://github.com/react-chatbotify-plugins/input-validator)
+- [**Markdown Parser**](https://github.com/react-chatbotify-plugins/markdown-parser)
+- [**llm-connector**](https://github.com/react-chatbotify-plugins/llm-connector) (WIP)
+- [**discord-live-chat**](https://github.com/react-chatbotify-plugins/discord-live-chat) (WIP)
 
-If you strongly believe that there are common use cases with no suitable plugins, you may feel free to make a suggestion for one on [**discord**](https://discord.gg/6R4DK4G5Zh).
+If you strongly believe that there are common use cases with no suitable plugins, you may feel free to make a suggestion for one on [**discord**](https://discord.gg/J6pA4v3AMW).
 
 For instructions on using plugins (both official or community-based), please refer to the plugin's documentation. Note that the maintenance of plugins are **separate** from the maintenance of the core React ChatBotify library.
 
 :::tip Tip
 
-Most plugins tend to rely on specific chatbot [**settings**](/docs/api/settings) for their logic (e.g. [**events**](/docs/api/events)). Ideally, plugin developers should provide auto-setup options out of the box. If not, make sure you read the plugin's setup instructions in detail to understand which settings are required to be enabled!
+Most plugins tend to rely on specific chatbot [**settings**](/docs/api/settings) for their logic (e.g. [**events**](/docs/api/events)). Ideally, plugin developers should provide auto-config options out of the box. If not, make sure you read the plugin's setup instructions in detail to understand which settings are required to be enabled!
 
 :::