Manage Focus for Accessibility 508 Compliance

This patch sets focus to the last element the user altered. It should probably be in an event handler or callback. If someone wants to improve this patch, please do.

I'm adding the patch file here too, not quite familiar with the protocol for MRs vs patches.

I'm adding another patch version here with a longer setTimeout because the animation is set to 400, and I've noticed some issues with the focus failing because the next select has not loaded yet.

Let's try that again. Not sure what happened with that diff.

Successfully tested patch #8: After applying the patch and navigating with keyboard/mouse focus is corrected.

There was an issue with the first item getting focus immediately on page load. This is a revised patch that checks the item level to make sure the field only gets focus if it is not the top level (i.e., on page load.)

I tested with patch #10 using keyboard navigation with VoiceOver and the focus states are correct now.

After reviewing accessibility documentation, it appears that the best method here is to stay on the selected item. Because the content is being added after the selection, a user will still be able to find it without have the function move the focus to the next item. I do however think this patch should move from the `ContainerView.js` file to the `WidgetView.js` file instead so it lives with the selection change code.

Fixing comment format.

I re-tested the updated patch in #14 and verified it works as intended.

Reviewed and Tested patch #14. Working as intended.

This is committed to dev, it'll make it into a release some time later, not sure when exactly.

Automatically closed - issue fixed for 2 weeks with no activity.