fix: handle new virtual legacy-polyfill name (#157)

The entry of the legacy-polyfill name has changed to start with a
\u0000 character to mark it as a virtual entry in vite 2.7.
This commit ensures that this new name is handled correctly.

See: #156

test/test_app/public/vite-production/manifest.json

@@ -41,7 +41,7 @@
   "_log.d31acc25-legacy.js": {
     "file": "assets/log.d31acc25-legacy.js"
   },
-  "../../vite/legacy-polyfills": {
+  "../../\u0000vite/legacy-polyfills": {
     "file": "assets/polyfills-legacy.07477394.js",
     "src": "../../vite/legacy-polyfills",
     "isEntry": true
@@ -100,4 +100,4 @@
   "_log.818edfb8.js": {
     "file": "assets/log.818edfb8.js"
   }
-}
+}

vite_ruby/lib/vite_ruby/manifest.rb

@@ -147,9 +147,11 @@ def resolve_references(manifest)
 
   # Internal: Resolves the manifest entry name for the specified resource.
   def resolve_entry_name(name, type: nil)
-    name = with_file_extension(name.to_s, type)
+    unless name.include?('legacy-polyfills')
+      name = with_file_extension(name.to_s, type)
 
-    raise ArgumentError, "Asset names can not be relative. Found: #{ name }" if name.start_with?('.') && !name.include?('legacy-polyfills')
+      raise ArgumentError, "Asset names can not be relative. Found: #{ name }" if name.start_with?('.')
+    end
 
     # Explicit path, relative to the source_code_dir.
     name.sub(%r{^~/(.+)$}) { return Regexp.last_match(1) }