add support for markdown description in clickup create task action

[RandallKent]

trafficstars

WHAT

copilot:summary

copilot:poem

WHY

Closes #9429

HOW

copilot:walkthrough

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
pipedream-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 10, 2024 8:47pm
pipedream-docs-redirect-do-not-edit	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 10, 2024 8:47pm

[pipedream-component-development]

Thank you so much for submitting this! We've added it to our backlog to review, and our team has been notified.

[pipedream-component-development]

Thanks for submitting this PR! When we review PRs, we follow the Pipedream component guidelines. If you're not familiar, here's a quick checklist:

• [ ] Create components to address specific use cases whenever possible
• [ ] Component keys should follow the format app_name_slug-slugified-component-name
• [ ] Components should follow the standard directory structure
• [ ] Prefer Node.js client libraries to REST APIs
• [ ] When making API requests, handle pagination to ensure all data / events are processed
• [ ] Use secret props to capture sensitive data
• [ ] Props and methods should be defined in app files whenever possible
• [ ] Document methods with JS Docs
• [ ] Use optional props whenever possible, and set a default value where you can
• [ ] Use async options to accept user input wherever possible

[GTFalcao]

@RandallKent I've applied these adjustments and moved the issue forward. You should merge with pipedream's master branch to update your own so that all the checks can run successfully. I've opened a PR in your fork for this: https://github.com/RandallKent/pipedream/pull/1

[vunguyenhung]

Hi everyone, all test cases are passed! Ready for release!

Test report https://vunguyenhung.notion.site/add-support-for-markdown-description-in-clickup-create-task-action-9430-6c80c82f48784b6c97d8396b6eae3e19