refactoring; migrating away from a dedicated macro for every html element

Author: RandomHashTags

Package.swift

@@ -20,9 +20,19 @@ let package = Package(
         .package(url: "https://github.com/apple/swift-nio", from: "2.75.0")
     ],
     targets: [
+        .macro(
+            name: "HTMLKitUtilityMacros",
+            dependencies: [
+                .product(name: "SwiftCompilerPlugin", package: "swift-syntax"),
+                .product(name: "SwiftDiagnostics", package: "swift-syntax"),
+                .product(name: "SwiftSyntax", package: "swift-syntax"),
+                .product(name: "SwiftSyntaxMacros", package: "swift-syntax")
+            ]
+        ),
         .target(
             name: "HTMLKitUtilities",
             dependencies: [
+                "HTMLKitUtilityMacros",
                 .product(name: "NIOCore", package: "swift-nio")
             ]
         ),

README.md

@@ -119,7 +119,7 @@ Using String Interpolation.
 > 
 > Its up to you whether or not to suppress this warning or escape the HTML at runtime using a method described above.
 > 
-> Swift HTMLKit tries to [replace](https://github.com/RandomHashTags/swift-htmlkit/blob/94793984763308ef5275dd9f71ea0b5e83fea417/Sources/HTMLKitMacros/HTMLElement.swift#L423) known interpolation at compile time with a compile time equivalent for the best performance. It is currently limited due to macro expansions being sandboxed and lexical contexts/AST not being available for macro arguments. This means referencing content known at compile time in a html macro won't get replaced by its literal contents. [Read more about this limitation](https://forums.swift.org/t/swift-lexical-lookup-for-referenced-stuff-located-outside-scope-current-file/75776/6).
+> Swift HTMLKit tries to [promote](https://github.com/RandomHashTags/swift-htmlkit/blob/94793984763308ef5275dd9f71ea0b5e83fea417/Sources/HTMLKitMacros/HTMLElement.swift#L423) known interpolation at compile time with an equivalent `StaticString` for the best performance. It is currently limited due to macro expansions being sandboxed and lexical contexts/AST not being available for macro arguments. This means referencing content known at compile time in a html macro won't get replaced by its literal contents. [Read more about this limitation](https://forums.swift.org/t/swift-lexical-lookup-for-referenced-stuff-located-outside-scope-current-file/75776/6).
 
 #### Example
 ```swift