feat(analytic): support to use custom server for analytics

[mynktl]

What this PR does?: This PR refactors the usage package APIs.

Caller can use the following updated API to send analytics to google:

• To create the usage builder object usage.New()
• To build the usage object usage.New().Build()
• To send the application analytic usageObj.ApplicationBuilder().Send()
• To send the installation analytic usageObj.InstallBuilder(true).Send()

Does this PR require any upgrade changes?: No

If the changes in this PR are manually verified, list down the scenarios covered::

Any additional information for your reviewer? : Mention if this PR is part of any design or a continuation of previous PRs

Checklist:

• [ ] Fixes #
• [x] PR Title follows the convention of <type>(<scope>): <subject>
• [ ] Has the change log section been updated?
• [ ] Commit has unit tests
• [ ] Commit has integration tests
• [ ] (Optional) Are upgrade changes included in this PR? If not, mention the issue/PR to track:
• [ ] (Optional) If documentation changes are required, which issue on https://github.com/openebs/openebs-docs is used to track them:

[kmova]

This PR needs update in all the dependent repos. This will be taken up as part of the next release.

[vharsh]

This PR needs update in all the dependent repos. This will be taken up as part of the next release.

Is moving it out into a separate feature-repo not in the plan, such that this becomes a vendor-ed library so that effort is reduced to a simple dependency version bump up? Was the earlier plan modified because of different ways each module will expose the .version variable location in constants of the binary?

[kmova]

this is not required anymore.