revert: Use generic patterns in integration tests without version constraints

- Revert exact version assertions where UpdateDependency gets latest version
- Keep generic patterns \d+\.\d+\.\d+ and [a-f0-9]{40} for future-proof tests
- Integration tests call UpdateDependency without pattern constraints
- Latest version will change over time (0.11.0 → 0.12.0, etc.)
- Unit tests can keep exact values since they specify exact versions

Author: vaind

updater/tests/update-dependency.Tests.ps1

@@ -275,7 +275,7 @@ FetchContent_MakeAvailable(sentry-native)
 
             $content = Get-Content $testFile -Raw
             $content | Should -Not -Match 'v0.9.1'
-            $content | Should -Match 'GIT_TAG 0\.11\.0'
+            $content | Should -Match 'GIT_TAG \d+\.\d+\.\d+'
             $content | Should -Match 'GIT_REPOSITORY https://github.com/getsentry/sentry-native'
         }
 
@@ -298,7 +298,7 @@ FetchContent_MakeAvailable(sentry-native)
 
             $content = Get-Content $testFile -Raw
             $content | Should -Not -Match 'v0.9.0'
-            $content | Should -Match 'GIT_TAG 0\.11\.0'
+            $content | Should -Match 'GIT_TAG \d+\.\d+\.\d+'
         }
 
         It 'updates from hash to newer tag preserving hash format' {
@@ -320,7 +320,7 @@ FetchContent_MakeAvailable(sentry-native)
 
             $content = Get-Content $testFile -Raw
             # Should update to a new hash with tag comment
-            $content | Should -Match 'GIT_TAG 3bd091313ae97be90be62696a2babe591a988eb8 # 0\.11\.0'
+            $content | Should -Match 'GIT_TAG [a-f0-9]{40} # \d+\.\d+\.\d+'
             $content | Should -Not -Match 'a64d5bd8ee130f2cda196b6fa7d9b65bfa6d32e2'
         }