The internal code from Metadata service is shown under Top Level namespace in docs

[trivikr]

Confirm by changing [ ] to [x] below to ensure that it's a bug:

• I've gone through Developer Guide and API reference
• I've checked AWS Forums and StackOverflow for answers
• I've searched for previous similar issues and didn't find any solution
• This is an issue with version 2.x of the SDK

Describe the bug
The Metadata service Endpoints are shown under Top Level namespace in docs.

Is the issue in the browser/Node.js?
Docs

If on Node.js, are you running this on AWS Lambda?
N/A

Details of the browser/Node.js version
N/A

SDK version number
N/A

To Reproduce (observed behavior)
View Top Level namespace in the docs.

Expected behavior
The internal code used by Metadata Service should either be published under MetadataService namespace, or it shouldn't be published at all.

Screenshots

Screenshot

[trivikr]

This happens as anything with module {} gets added to top level workspace.
We will move internal code used by metadata_service under namespace AWS.MetadataService.

[trivikr]

Experimental PR was posted at #3953
A quick solution appears to be moving all source code under metadata_service.js just like other files which contain all the source code.