Refresh keys when refreshing submissions

[ktuite]

Closes #521

When submissions are refreshed, if we might need to refetch an encryption key (if the form is encrypted and we have no keys at the moment), then the submission list component will emit an event to the parent component, which is already responsible for the initial key request, to refetch the key.

What has been done to verify that this works as intended?

Tests

Why is this the best possible solution? Were any other approaches considered?

Keys are loaded in two places, maybe that's not great.

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

Should fix an issue, shouldn't really be any risks. Keys (a small chunk of data) are fetched more often now, but in a way that seems necessary and useful.

Does this change require updates to user documentation? If so, please file an issue here and include the link below.

Before submitting this PR, please make sure you have:

• run npm run test and npm run lint and confirmed all checks still pass OR confirm CircleCI build passes
• verified that any code or assets from external sources are properly credited in comments or that everything is internally sourced

[ktuite]

Code review with @matthew-white