Migrate featureFlags/getFeatureFlag and graphql/getCurrentUserCodySubscription

[mkondratek]

This PR is a part of the protocol migration. Some endpoints are written by hand. We are switching to the protocol generated from Cody. In this PR:

• Migrate featureFlags/getFeatureFlag
• Migrate graphql/getCurrentUserCodySubscription

Based on PR #2630

Full chain of PRs as of 2024-11-13

• PR Migrate featureFlags/getFeatureFlag and graphql/getCurrentUserCodySubscription #2632:
  mkondratek/chore/migrate-api-part-1 ➔ mkondratek/chore/update-deps
• PR Update dependencies #2630:
  mkondratek/chore/update-deps ➔ main

Test plan

• Verified with debugger - the server returns proper values.
• Verified with debugger - with the mocked results the notification about the ended trial appears

[mkondratek]

We can consider renaming this class.

We should consider options to automatically generate the values of the enums.

However, I think we can simply remove what is redundant now. It will be no worse. Then, having less code it will be easier to improve the generation.

[pkukielka]

I think we should put it in protocol_extensions package.

[pkukielka]

Also, if we are only using two values from each enum we could consider using extension methods instead:

fun CurrentUserCodySubscription.isProPlan() {
   return plan == "PRO"
}

fun CurrentUserCodySubscription.isPendingStatus() {
   return status == "PENDING"
}

and then on the call site e.g.:

currentUserCodySubscription.isProPlan() instead of
currentUserCodySubscription.status == GetCurrentUserCodySubscription.Status.PENDING

Then we won't need custom objects like GetCurrentUserCodySubscription. But it is also fine as it is.

[mkondratek]

makes sense ! thanks

[mkondratek]

fixed!

[pkukielka]

LGTM