consider qualifying common module names

[tayloraswift]

this library currently uses a number of common module names:

• DOM
• SVG
• FileSystem
• WebSockets

DOM and SVG are likely to be used by renderers, FileSystem by file system utilities, and WebSockets with networking libraries.

this library doesn’t really implement SVG, it implements manipulating SVG from JavaScript. so i think JavaScriptSVG or SVG_JavaScript is a better name for that module. and so forth for the other three modules.

this can be sort of avoided today using Module Aliases, but that makes it hard to discuss the library in documentation when using automated linking tools. for example, we might want to write a tutorial over at Swift on Server articles about the client and server sides of a WebAssembly application, and colliding module names would make it challenging to write such an article.