Config & Config UI for App Refresh Query

[teallarson]

Change description

• config files now use the structure:

  "refresh" : {
    "query": "...",
    "recurringFrequency": 60000
  }

• Config UI fixes (don't show the currently saved values or "run" button, query gets saved to file correctly now)
• Fixed UI to default to "Edit" state upon creating a new App Refresh Query. Also fixed issue with React intermittently locking the object for "undefined" values for appRefreshQuery.locked and app.locked
• appRefreshQuery:run task is enqueued immediately if the query is updated on the model

New Config UI for App Refresh Query:

Checklists

Development

• Application changes have been tested appropriately

Impact

• Code follows company security practices and guidelines
• Security impact of change has been considered
• Performance impact of change has been considered
• Possible migration needs considered (model migrations, config migrations, etc.)

Please explain any security, performance, migration, or other impacts if relevant:

Code review

• Pull request has a descriptive title and context useful to a reviewer. Screenshots or screencasts are attached where applicable.
• Relevant tags have been added to the PR (bug, enhancement, internal, etc.)

[teallarson]

@evantahler one question on this PR... I'm not sure that there are customers using an app refresh query in production, but if there were, this would be breaking I believe because of the rename. How do we do migrations for code config?

[evantahler]

I think that for expediency's sake, it's a safe assumption that folks are not yet using code-config (as we haven't announced it yet). I wouldn't focus on a code-config migration at this time.

@bleonard - does that work for you?