Experimental API 1 - Supporting calls

## Background
1st part of the API rewrite.
Approach this as a PoC.
API is enough. Do not touch UI.
Think about where Envelope makes sense

## Feature
Create a new "branch" of API calls. New namespace.
All of this should be put under profile "api-experimental" in spring or a feature switch

- root of the calls is /api-experimental
- Returns object with metadata like version, even name, spark version
- /hdfs changes to /storage
- would provide storage settings/metadata for the Menas. What is enabled and queried
- /list would be the hdfs/list and would get dir structures
- Param 1 - source (hdfs, s3)
- Param 2 - path
- Param 3 - optional bucket
- /user remains /user
- Remove the /version from it
- Remove Mena’s version from userInfo
- Print proper User info -> Name, Logged in at, Token Valid until
- /oozie remains /oozie
- /isEnabled moves under the root call and gives some status messages
- /runNow is renamed to either run-now or run
- /suspend, /resume and coordinator status change to be under /coordinator
- Under /coordinator/{id} you can ge the oozie schedule
- Under /coordinator/{id}/suspend you can find former suspend
- Under /coordinator/{id}/resume you can find former resume
- Under /coordinator/{id}/status you can find former coordinatorStatus
- /monitoring changes into /statistics
- /statistics get you the daily statistics for landing page
- /statistics/{dataset} gets you monitoring for the last week for the dataset
- /statistics/{dataset}/{startDate} gets you monitoring for the week between startDate till startDate + 7 days for the dataset
- /statistics/{dataset}/{startDate}/{endDate} gets you monitoring for the time specified.