Branch: master

      Updated implementation such that if on an environment where the application
      is deployed SMTP Gmail in unsupported the instead of sending an email
      to accept the Mquest the mentor-mentee gets directly connected
      immediately after Mquest is created.

      Heroku doesn't support sending emails using SMTP Gmail settings, thus
      this alternative is taken.This way there would not be any dependency
      on client to have multiple email accounts to test out the features involving
      sending/receiving emails.

============= Updated

     /config/settings.yml
      - Added variable:
          mail_settings_available: ENV['MAIL_SETTINGS_AVAILABLE']

     /app/controllers/mquests_controller.rb
      - Refactored code in method: accept by moving out the code creating
        mentor-mentee connection to private method: create_mentor_mentee_connection(mquest)

      - Updated implementation in method: create.
        Added following code to be executed in case Mail settings are unavailable
        for sending emails:

          mail_settings_available = Settings.try(:mail_settings_available)
          if (!mail_settings_available.nil? and !mail_settings_available)
            create_mentor_mentee_connection(mquest)

            # Ignore the message returned by create_mentor_mentee_connection(mquest) method
            # It returns success message in context of who mquest receiver accepting
            # the mquest.And for immediate linking the message should be in context
            # of current logged in user.
            message = t('user.mentor_mentee_connection.messages.success', { role: mquest.as_role, user_name: mquest.receiver.name })

            redirect_to user_mquests_path(current_user), flash: { notice: message }
            return
          end