Fixes #14097 - Only run DatabaseCleaner truncation on JS tests

Problem:
DatabaseCleaner runs after all integration tests, on truncation mode.
However, for tests where we use rack-test instead of poltergeist, this
is not necessary and slows down the test suite....

Fixes #5883 - Reflect token expiry in build status

The Global Status introduced in recent Foreman releases makes it easy to
mark the build status as erroneous if the token has expired. This drags
attention to the fact that the host will not be able to mark itself as...

Fixes #13557 - Rubocop enforce specifying a timezone

Rubocop can enforce what timezone to store in the database ,
so we can ensure everything is stored using UTC and we don't
miss these things in code reviews. When objects are displayed,
they must use the time provided by set_timezone in the...

fixes #13112 - add options to HostStatus#relevant? to optimise reports

To match other methods on HostStatus::Status instances, relevant? has a
new options argument which is used from the global status building to
optimise config report loading. This prevents an N+1 query on the...

fixes #12954 - config status is relevant if reports exist or via setting

For a host that has config management reports, but no Puppet proxy set,
consider the config status relevant. This helps in an environment with
reports but no proxy, but has the side effect of considering the status...

Fixes #12728 - Add attr_accessible to Report

fixes #11771 - ensure created HostStatuses are saved correctly

The HostStatus reported_at timestamp is now validated to match the DB
schema and populated if it's missing. HostStatus subclasses should
validate correctly without needing to call #refresh.
...

fixes #11833 - remove puppet references from config status

Fixes #11791 - avoid N+1 query caused by configuration status

Fixes #11704 - consider no reports as warning if reports are expected