BridgeJS: chore: extend docc documentaion with namespace example

Author: krodak

Sources/JavaScriptKit/Documentation.docc/Articles/Exporting-Swift-to-JavaScript.md

@@ -162,3 +162,93 @@ export type Exports = {
     }
 }
 ```
+
+## Using Namespaces
+
+The `@JS` macro supports organizing your exported Swift code into namespaces using dot-separated strings. This allows you to create hierarchical structures in JavaScript that mirror your Swift code organization.
+
+### Functions with Namespaces
+
+You can export functions to specific namespaces by providing a namespace parameter:
+
+```swift
+import JavaScriptKit
+
+// Export a function to a custom namespace
+@JS("MyModule.Utils") func namespacedFunction() -> String { 
+    return "namespaced" 
+}
+```
+
+This function will be accessible in JavaScript through its namespace hierarchy:
+
+```javascript
+// Access the function through its namespace
+const result = globalThis.MyModule.Utils.namespacedFunction();
+console.log(result); // "namespaced"
+```
+
+The generated TypeScript declaration will reflect the namespace structure:
+
+```typescript
+declare global {
+    namespace MyModule {
+        namespace Utils {
+            function namespacedFunction(): string;
+        }
+    }
+}
+```
+
+### Classes with Namespaces
+
+For classes, you only need to specify the namespace on the top-level class declaration. All exported methods within the class will be part of that namespace:
+
+```swift
+import JavaScriptKit
+
+@JS("__Swift.Foundation") class Greeter {
+    var name: String
+
+    @JS init(name: String) {
+        self.name = name
+    }
+
+    @JS func greet() -> String {
+        return "Hello, " + self.name + "!"
+    }
+
+    func changeName(name: String) {
+        self.name = name
+    }
+}
+```
+
+In JavaScript, this class is accessible through its namespace:
+
+```javascript
+// Create instances through namespaced constructors
+const greeter = new globalThis.__Swift.Foundation.Greeter("World");
+console.log(greeter.greet()); // "Hello, World!"
+```
+
+The generated TypeScript declaration will organize the class within its namespace:
+
+```typescript
+declare global {
+    namespace __Swift {
+        namespace Foundation {
+            class Greeter {
+                constructor(name: string);
+                greet(): string;
+            }
+        }
+    }
+}
+
+export interface Greeter extends SwiftHeapObject {
+    greet(): string;
+}
+```
+
+Using namespaces can be preferable for projects with many global functions, as they help prevent naming collisions. Namespaces also provide intuitive hierarchies for organizing your exported Swift code, and they do not affect the code generated by `@JS` declarations without namespaces.