Use event handler for creating Yaga settings page

This creates the core Yaga settings page as a method on the dashboard
settings controller instead of having the page be its own controller.
Flesh out the README installation instructions
That sentence turned out a bit awkward...
Display reaction record on profile reaction list items
Correctly distinquish between parent types to avoid ID clashes

When selecting content that has been reacted to, discussion and comment
IDs will currently clash. E.g. if comment #16 has been reacted to, the
acted model will also query discussion #16 if it exists.

This commit fixes the bug by taking into account the reaction parent
types. The data was already available but wasn't being used.
Add .gitignore
Ensure EOF newline
Merge pull request #8 from kasperisager/actedmodel-content-type-fix

Thanks for catching my oversight. :D
Merge pull request #9 from kasperisager/gitignore

Add .gitignore
Merge pull request #7 from kasperisager/profile-reaction-record

Display reaction record on profile reaction list items
Optimize check for enable
Merge pull request #6 from kasperisager/readme-additions

Readme additions from Kasper.

Looks good!
Merge pull request #4 from kasperisager/core-settings-refactor

Implement the Yaga settings page as an extension to the settings controller.
Updated rule descriptions and fixed some locale errors.
Add some tooltip text on the reaction record profile links