Add early return when offset range is unavailable in no-invalid-scriptlets rule fuzzy matching

- Added null check for `context.getOffsetRangeForNode(node)` before processing fuzzy match suggestions
- Moved range calculation before fuzzy matching logic to avoid unnecessary processing
- Changed `fixer.replaceWithText` to use validated range instead of `[node.start!, node.end!]`
- Prevents potential errors when node offset range cannot be determined

Author: scripthunter7

src/rules/no-invalid-scriptlets.ts

@@ -242,6 +242,12 @@ export default defineRule({
                     scriptletData = scriptletsCompatibilityTable.getFirst(scriptletName, platform);
 
                     if (scriptletData === null) {
+                        const range = context.getOffsetRangeForNode(node);
+
+                        if (range === null) {
+                            return;
+                        }
+
                         const names = getScriptletNames(platform);
                         const possibleMatches = search(
                             scriptletName,
@@ -267,7 +273,7 @@ export default defineRule({
                                 },
                                 fix(fixer) {
                                     return fixer.replaceWithText(
-                                        [node.start!, node.end!],
+                                        range,
                                         QuoteUtils.setStringQuoteType(match, actualQuote),
                                     );
                                 },