Refactoring and adding some spec for the user and entries model
1. Removed the 'percieved' behavior from entry model. It was a code that
was related to user interface. It should not live in domain object.
Instead it belongs in a view helper. Moved it accordingly and added a
test for the helper
2. A simple spec can be demonstrated for user, to show that user can
have multiple entries or none. Thats pretty much you can test in respect
to entries now. No other domain logic present as of yet
3. Added a spec in controller to check if entry being deleted currently
belongs to the current user. If not, then an error is thrown. This
represents the kind of use cases that should be tested in controller.