Version1.0 --- core functions work in progress

- User can now create their own kitchen
- User can now see all the listed kitchen
- User can now delete and edit their own kitchen
- User can now submit reservations for kitchen
- User can now see reservations submitted by themselves
- If user click "delete" kitchen, it will change kitchen.data_status to "archive" and no longer be displayed; it WILL NOT destroy the record from database

A few things.

1.  Ultimately, you should use `Enumerable#group_by`.
2.  It's better to define methods on the model like

    ```ruby
    class Reservation < ActiveRecord::Base
      scope :approved, lambda { where(:status => 'approved') }

      def approved?
        status == 'approved'
      end
    end
    ```

    and so on.  Try not to expose so much internal state to the calling environment.