docs: drop provenance terminology from README and a test comment

DataJoint's own docs use the relational workflow model's vocabulary
(lineage, reproducibility); provenance is a platform-level compatibility
concern documented separately.

Author: dimitri-yatsenko

README.md

@@ -5,7 +5,7 @@ DataJoint is a framework for scientific data pipelines based on the **Relational
 - **Tables represent workflow steps** — Each table is a step in your pipeline
 - **Foreign keys encode dependencies** — Parent tables must be populated before child tables
 - **Computations are declarative** — Define *what* to compute; DataJoint handles *when*
-- **Results are immutable** — Full provenance and reproducibility
+- **Results are immutable** — Full lineage and reproducibility
 
 **Documentation:** https://docs.datajoint.com
 

tests/integration/test_autopopulate.py

@@ -381,7 +381,7 @@ class Greeting(dj.Computed):
         """
 
         def make(self, key):
-            # Provenance-safe read: self.upstream pre-restricted to current key
+            # Upstream read: self.upstream pre-restricted to current key
             name = self.upstream[Subject].fetch1("name")
             self.insert1({**key, "greeting": f"Hello, {name}!"})