[Feature flag] Enable pass_jtbd_longtail_desc_to_workato

<!-- Title suggestion: [Feature flag] Enable description of feature -->

# Summary

<!-- Short description of what the feature is about and link to relevant other issues. -->

This issue is to rollout [Pass long tail description as jtbd when create Workato lead
](https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/5452) on CustomersDot production,
that is currently behind the [pass_jtbd_longtail_desc_to_workato](https://gitlab.com/gitlab-org/customers-gitlab-com/-/feature_flags/190/edit) feature flag.

## Owners

- Team: ~"group::commerce integration" 
- Most appropriate Slack channel to reach out to: `#g_commerce_integrations`
- Best individual to reach out to: @qzhaogitlab 
- PM: @courtmeddaugh 

## Stakeholders

- @MihaiConteanu 

## The Rollout Plan

- Rollout Feature for everyone as soon as it's ready

<!-- Which dashboards from https://dashboards.gitlab.net are most relevant? Sentry errors reports can also be useful to review -->


## Expectations

### What are we expecting to happen?

Workato lead creation endpoint receives payload `jbtd: <long tail description>` instead of `jbtd: <api reason>`.

### What might happen if this goes wrong?

If anything wrong, we can disable the feature flag [pass_jtbd_longtail_desc_to_workato](https://gitlab.com/gitlab-org/customers-gitlab-com/-/feature_flags/190/edit)

If necessary, it is possible to write a script to update the Workato leads: 
- read lead attributes from CustomersDot Lead table
- call `Workato::CreateLeadService`

### What can we monitor to detect problems with this?

- No [reporting error](https://console.cloud.google.com/logs/query;query=logName%3D%2528%22projects%2Fgitlab-subscriptions-prod%2Flogs%2Fsidekiq.production%22%20OR%20%22projects%2Fgitlab-subscriptions-prod%2Flogs%2Frails.production%22%2529%0A%22Workato%22%20AND%20jsonPayload.success%20%3D%20false%0A;timeRange=P2D;cursorTimestamp=2023-01-05T22:31:43.123Z?project=gitlab-subscriptions-prod) related to this change
- Will ask @MihaiConteanu to confirm whether anything is wrong from Workato side. (We do not have access to Workato and downstream systems).

## Rollout Steps

### Rollout on non-production environments

- [x] Ensure that the feature MRs have been deployed to non-production environments, i.e. `customers-staging`.
- [x] Consider announcing that the flag will be enabled to potentially impacted groups, e.g. `#s_fulfillment_engineering`
- [x] Enable the feature globally on non-production environments by applying the appropriate environment, e.g. `customers-staging` and `customers-development`.
- [x] Notify the Software Engineers in Test (SETs) for Fulfillment via Slack and in a comment in this issue when enabling a feature flag in `customers-staging` as it can impact the QA pipeline.
- [x] Verify that the feature works as expected. Posting the QA result in this issue is preferable.

### Preparation before production rollout

- [x] Ensure that the feature MRs have been deployed to production
- [x] Check if the feature flag change needs to be accompanied with a
  [change management issue](https://about.gitlab.com/handbook/engineering/infrastructure/change-management/#feature-flags-and-the-change-management-process) -- Not needed.
  Cross link the issue here if it does.
- [x] Ensure that you or a representative in Fulfillment can be available for at least 2 hours after feature flag updates in production.
  If a different developer will be covering, or an exception is needed, please inform the Fulfillment team in #s_fulfillment_engineering
- [x] Ensure any documentation has been updated -- Not needed
- [x] Announce on [the feature issue](ISSUE LINK) an estimated time this will be enabled on production if applicable
- [ ] If the feature might impact the user experience, notify `#s_fulfillment` and potentially  `#support_gitlab-com`, as well as your team channel ([more guidance when this is necessary in the dev docs](https://docs.gitlab.com/ee/development/feature_flags/controls.html#communicate-the-change)). -- Not needed

### Global rollout on CustomersDot production

- [x] Confirm the feature flag is enabled on `staging` without incident
- [ ] Roll out the feature to targeted testing users first (if applicable)
- [ ] If applicable, [incrementally roll out](https://docs.gitlab.com/ee/operations/feature_flags.html#percent-rollout) the feature.
- [ ] Verify the change has the desired outcome with the limited rollout before enabling the feature globally on production.
- [x] Enable the feature globally on production environment
- [x] Announce on [the feature issue](ISSUE LINK) that the feature has been globally enabled.
- [x] Wait for [at least one day for the verification term](https://about.gitlab.com/handbook/product-development-flow/feature-flag-lifecycle/#including-a-feature-behind-feature-flag-in-the-final-release).

### Release the feature

After the feature has been [deemed stable](https://about.gitlab.com/handbook/product-development-flow/feature-flag-lifecycle/#including-a-feature-behind-feature-flag-in-the-final-release),
the clean up should be done as soon as possible to permanently enable the feature and reduce complexity in the codebase.

<!-- The checklist here is to help stakeholders keep track of the feature flag status -->
- [x] Create a merge request to remove `<feature-flag-name>` feature flag
  - [x] Remove all references to the feature flag from the codebase
- [x] Ensure that the cleanup MR has been deployed to both staging and production
- [x] Disable the feature flag via the [CustomersDot dashboard](https://gitlab.com/gitlab-org/customers-gitlab-com/-/feature_flags)
- [x] Ensure production environment is still working as expected
- [x] Remove the Unleash feature flag from the [CustomersDot dashboard](https://gitlab.com/gitlab-org/customers-gitlab-com/-/feature_flags)
- [x] Close this rollout issue.

## Rollback Steps

- [ ] This feature can be disabled by performing the following actions:
  - [ ] Disable the Unleash flag on the [feature flag page](https://gitlab.com/gitlab-org/customers-gitlab-com/-/feature_flags/190/edit)

Story points: 1.0