UI: Bugs around dots in task/task-group/driver names

[DingoEatingFuzz]

There is a repeated pattern in serializers in the UI code of using Ember.get to read properties off of potentially undefined objects. Unfortunately, Ember.get doesn't perfectly match plain JavaScript in its allowance of property names: dots in Ember.get paths are always treated as nesting, meanwhile, dots are valid characters in properties in JavaScript and therefore JSON.

This PR adds a bunch of unit tests to the offending serializers to expose the bugs and then squashes all the bugs by removing this pattern.

1. Allocation: task names with dots caused a "cannot read property from an undefined object", resulting in an error page
2. Deployment: task groups with dots would silently not have the correct properties.
3. Evaluation: failed task groups with dots would silently not have the correct properties.
4. JobPlan: same as evaluations.
5. JobSummary: task groups with dots would silently not have allocation status properties.
6. Node: drivers with dots (there are none, but there could be in the future) would silently not have any properties, such as detected or healthy.

[meirish]

You'll be glad to know new testing doesn't have needs 🎉

[DingoEatingFuzz]

I can't wait.

[meirish]

We've had to work around this a few times as well 😬 - very straightforward implementation here though and 👍 nice table tests ✨.

[github-actions]

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.