Make the frozen_string Danger check more resilient

It's possible for a Ruby file to be empty and thus gets returns nil.

Also indents the Markdown since we're using <<~ and removes an unneeded variable.

Resolves a possible error as seen in https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/6669#note_90381400.