This commit resolves #232, resolves #264, resolves #268.

#232
- GoogleCloudService is restructured to support back-up action
- 'backup' : put all recording items into recordinSet(which is a set of archiving-approved-recordings)
- 'retry' : upload all items in the recordingSet.
- [recording-item ID] : upload the corresponding recording item.
- Archiving-process-state
  (0: Archive-approved, 1: File uploaded to GoogleDrive, 2: Indexed in FusionTable and '-archive.json' file is created)
- '-archive.json' format: File's name, group-ID, archive-finish date

#264
- During the recording is in progress, the screen is turned on continuously

#268
- when the access token is obtained, it is always validated by Google
- If the key is not valid, new token is issued and used.
- Previously used Google-account and Access-token are stored in Preference and used again without user's intervention next time.
- GoogleCloudService is started after the token is obtained.(in onPostExecute of GetTokenTask)
I used GoogleAuth to check if the access token is valid.
(So if GoogleAuth.validateAccessToken(access_token) is false, the app tries to refresh access_token)