[B] Convert the remaining graphQL tag function calls over to normal function calls to alleviate the memory leak

[ericdrosas87]

Expected Behavior

GraphQL queries do not cause memory leaks

Actual Behavior

GraphQL queries initiated as tag functions are causing memory leaks. Alex cleaned up most of them, but some still remain.

Steps to Reproduce the Problem

1. Monitor client pod memory usage over time in the production cloud dashboard

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
The mitigation for the time-being is to restart the deploy periodically, but this is unsustainable. A later task converting the newly converted normal function calls to typed calls will be created and worked.