Fixes #53 Rename "name" to "plugin_id" and "prettyName" to "name"

[ravi-cm]

Pull request checklist

Please check if your PR fulfills the following requirements:

• [x]Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• Build was run locally and any changes were pushed
• Lint has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):
  SDK changes to reflect the backend changes to rename name->id and prettyName->name.

1. Removed the plugin_config_schema which skipped id validation. Also removed the skip-id-validation flag in CLI.
2. Changed artifact creation to include pluginId and name fields per the new schema.
3. Adjusted unit tests where required.
4. Changed dvp download-logs to use plugin/toolkit identifier to match the required plugin when downloading logs.

What is the current behavior?

artifact has "name" and "prettyName" fields which are renamed now on the backend side.
Issue Number: 53

What is the new behavior?

• artifact will now have pluginId and name fields to match the engine schema.

Does this introduce a breaking change?

• Yes
• No

Old plugins need to be built with new SDK to upload to a newer engine.

Other information

1. Tested with a plugin build with this new changes and uploaded to DE.
2. Tested download logs with the new changes.
3. Tested plugin upgrade by uploading to an engine that already has an old plugin (built without these changes).
4. Tested by trying upload to an older engine and made sure failure is reported.

[ravi-cm]

Tested w/ engine changes and new SDK changes.