Fix dashboard to refresh visualizations when the refresh button is clicked

[lukasolson]

Summary

Fixes #23329.

This PR updates dashboard so that clicking on the refresh button actually refreshes visualizations.

As of #19172, visualizations don't inherit from the dashboard's search source. As a result, when the search source is updated (even when clicking on the "refresh" button), they don't automatically get the new data that's fetched.

This PR adds an additional property to some of the dashboard components that allows parent components to call reload() programmatically, rather than only when state changes happen.

Honestly I'm not too thrilled with this change, so I'm open to feedback about other ways we could accomplish this same thing. As far as I could tell the only mechanism for communication between the panels and the dashboard was via state changes.

Checklist

Use strikethroughs to remove checklist items you don't feel are applicable to this PR.

• This was checked for cross-browser compatibility, including a check against IE11
• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• This was checked for keyboard-only and screenreader accessibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately
• This includes a feature addition or change that requires a release note and was labeled appropriately

[elasticmachine]

Pinging @elastic/kibana-app

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[lukasolson]

Looks like I need to update some tests and add one to test this behavior.

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[timroes]

Honestly I'm not too thrilled with this change, so I'm open to feedback about other ways we could accomplish this same thing. As far as I could tell the only mechanism for communication between the panels and the dashboard was via state changes.

I personally like the idea of having an explicit reload method on the embeddables. I think that is the better long term solution since we're trying to have everything between the outer layer and the inner embeddable passed and handled explicitly, rather than just triggering some events on some underlying classes.

I am not yet familar enough with the dashboard code, to check if that's a good way to keep track of all the embeddables. Maybe @stacey-gammon could elaborate on that part of the code a bit?

[stacey-gammon]

The embeddables are all stored on the redux tree, so if you add a RELOAD action, I think you can do this without the registering/deregistering stuff, and I think without $scope.reload.

@lukasolson - lmk if you want to sync up and go over to see if we can do this without any extra angular stuff.

[lukasolson]

Closed in favor of #27353.