Fix tag CU chart when there are no daily data

[PanSpagetka]

Fix tag CU chart when there are not enough daily data.
I think, that source of this problem is hidden in generating reports, but because i think it is related to blocker bz, I just fix consequences and return to it later.

Links [Optional]

Related(ish) with https://bugzilla.redhat.com/show_bug.cgi?id=1540129

Steps for Testing/QA [Optional]

Select host with some C&U data, but not for all day.
Utilization -> Group By (tag) -> Daily

Screenshots

Before:

After:

[lgalis]

This does prevent the crash when there are no records with capture_interval_name = 'daily' but there are records with 'capture_interval_name = 'hourly' for multiple days.
there are specs errors with this change.
we need to look into the Interval field display - and how that relates to the hourly/daily data - and invalidate the group_by when there is no actual 'daily' utilization data

[miq-bot]

Checked commit PanSpagetka@570c904 with ruby 2.3.3, rubocop 0.52.0, haml-lint 0.20.0, and yamllint 1.10.0
1 file checked, 0 offenses detected
Everything looks fine. 👍

[mzazrivec]

@lgalis Are you OK with the proposed fix? Thanks.

[lgalis]

This PR fixes the crash, so I am OK with it. We can look at addressing the no-data situation better in a different PR upstream.