refactor!: separate expressions from execution plans && renames (#124)

# Rationale for this change
As the amount of expressions and execution plans increase we need to
seriously differentiate between the two. This PR is the first in a
series of PRs that will lead to `SliceExec` and `UnionExec`.
 
<!--
Why are you proposing this change? If this is already explained clearly
in the linked Jira ticket then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand
your changes and offer better suggestions for fixes.
-->

# What changes are included in this PR?
- rename `ProvableExpr` to `ProofExpr`
- rename `ProvableExprPlan` to `DynProofExpr`
- rename `AliasedProvableExprPlan` to `AliasedDynProofExpr`
- rename `ProvableExprPlanBuilder` to `DynProofExprBuilder`
- rename `ProofPlan` to `DynProofPlan`
- rename `ProofExecutionPlan` to `ProofPlan`
- move all `ProofExpr`s to `sql::proof_exprs`
- move all `ProofPlan`s to `sql::proof_plans`
- fix `Cargo.toml` warning in new Rust
 
<!--
There is no need to duplicate the description in the ticket here but it
is sometimes worth providing a summary of the individual changes in this
PR.
-->

# Are these changes tested?
Existing tests should pass
<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code

If tests are not included in your PR, please explain why (for example,
are they covered by existing tests)?
-->

crates/proof-of-sql/Cargo.toml

@@ -48,7 +48,7 @@ thiserror = { workspace = true }
 tracing = { workspace = true, features = ["attributes"] }
 zerocopy = { workspace = true }
 
-[dev_dependencies]
+[dev-dependencies]
 alloy-primitives = { workspace = true }
 alloy-sol-types = { workspace = true }
 arrow-csv = { workspace = true }

crates/proof-of-sql/src/base/database/accessor.rs

@@ -90,7 +90,7 @@ pub trait DataAccessor<S: Scalar>: MetadataAccessor {
 ///
 /// This accessor should be implemented by both the prover and verifier
 /// and then used by the Proof of SQL code to convert an IntermediateAst
-/// into a ProofExecutionPlan.
+/// into a ProofPlan.
 pub trait SchemaAccessor {
     /// Lookup the column's data type in the specified table
     ///

crates/proof-of-sql/src/base/proof/transcript_protocol.rs

@@ -149,7 +149,7 @@ pub enum MessageLabel {
     /// Represents challenges posted after result computation.
     PostResultChallenges,
     /// Represents a SQL query
-    ProofExecutionPlan,
+    ProofPlan,
     /// Represents the length of a table.
     TableLength,
     /// Represents an offset for a generator.
@@ -179,7 +179,7 @@ impl MessageLabel {
             MessageLabel::DoryMessage => b"dorymessage v1",
             MessageLabel::DoryChallenge => b"dorychallenge v1",
             MessageLabel::PostResultChallenges => b"postresultchallenges v1",
-            MessageLabel::ProofExecutionPlan => b"proofexec v1",
+            MessageLabel::ProofPlan => b"proofplan v1",
             MessageLabel::TableLength => b"tablelength v1",
             MessageLabel::GeneratorOffset => b"generatoroffset v1",
         }