domo: confirm OAuth scopes before building actions

Domo connects through a shared OAuth app that Pipedream manages centrally, not one specific to this integration — so the scopes it currently requests aren't visible from the component code, and adding new ones means updating that shared connection rather than something the component itself can control.

This needs to be resolved before the actions are built, or they won't have the access they need to work.

No file, test, or entry point is named. Start by locating the centrally managed shared OAuth connection for Domo and confirming which scopes it currently requests; done means the required scopes are confirmed or updated before the actions are built.

Written by the indexing model from the issue text.