Redesign the version check capability and include support for metrics collection

[Hemen Kapadia]

This is linked to issue #3

While redesigning the version check capability include a provision to capture the trends of people and how they use getbhavcopy.

Ideally I would like to capture the following information for every download operations

1. Date and Time of data download
2. Rage of data download
3. The data files requested in the download (NSE, BSE, Futures)
4. Optionally, extending point 3 above, we may want to capture all the options, but that could be an overkill.

The response would we simply the current version number, which would then start the actual download.

While the communication from the desktop client to the REST service be synchronous (i.e. wait for response for next steps to start), we would not want the REST service to block for the data to be written to the database. That part needs to be asynchronous, whereby the version response is sent to the client without waiting for the usage information to be written into the database.