Update sourcify-database.sql schema for upstream VerA changes

Author: manuelwedler

services/database/README.md

@@ -25,6 +25,7 @@ The migrations should be used to update the live Sourcify production and staging
 Schema changes should be made depending on the type of change:
 If they are a Sourcify extension, they should be made inside this repo.
 If they concern the Verifier Alliance schema, changes should be made in the Verifier Alliance [database-specs](https://github.com/verifier-alliance/database-specs) repository and then be pulled into this repository by updating the git submodule.
+After updating the submodule, the schema dump `sourcify-database.sql` should be updated by running the migrations from this repository.
 
 Any new migration should be capable of updating the live Sourcify staging and production databases.
 

services/database/sourcify-database.sql

@@ -1381,6 +1381,13 @@ CREATE INDEX compiled_contracts_sources_compilation_id ON public.compiled_contra
 CREATE INDEX compiled_contracts_sources_source_hash ON public.compiled_contracts_sources USING btree (source_hash);
 
 
+--
+-- Name: contract_deployments_address; Type: INDEX; Schema: public; Owner: -
+--
+
+CREATE INDEX contract_deployments_address ON public.contract_deployments USING btree (address);
+
+
 --
 -- Name: contract_deployments_contract_id; Type: INDEX; Schema: public; Owner: -
 --
@@ -1887,4 +1894,5 @@ ALTER TABLE ONLY public.verified_contracts
 
 INSERT INTO public.schema_migrations (version) VALUES
     ('20250717103432'),
-    ('20250722133557');
+    ('20250722133557'),
+    ('20250723145429');