feat: Elliptic Curve Virtual Machine Circuit

[zac-williamson]

…polynomial

permutation relation arithmetic defined exclusively in relationclasses

comments, naming cleanup

init

ecc_vm_relation_test, algebra test passes sumcheck relation test does not

wip

eccvm, shiftable polynomials now have 0 at first coefficient

added clearer comments to eccvm relations

removed redundant test files

eccvm composer test passes

eccvm flavor (+ upstream circuit builder) are parametrised by curve type / commitment scheme

wip

wip

wip

wip

reduced eccvm relation lengths

added more descriptive comments to ecc_set_relation

cleaned up sumcheck relation fowarding macros

added missing explicit template declarations

slight cleanup of method name bloat

added missing method

removed unused using declaration

added explicit lookup_library.hpp file to compute logderivative inverses

typo fix

formatting reversions

added ECCVM concepts to flavor

removed unused logderivative method

each subrelation can now choose to not scale relation term by random polynomial

permutation relation arithmetic defined exclusively in relationclasses

comments, naming cleanup

removed TypeMuncher from relation_types

remove foundation

blah compiler errors

compile error fix

compiler fix

compiler fix

wasm compiler fix

wasm compiler fix

compiler fix

compiler fix

fixed error in eccvm lookup relation

Description

Please provide a paragraph or two giving a summary of the change, including relevant motivation and context.

Checklist:

• I have reviewed my diff in github, line by line.
• Every change is related to the PR description.
• The branch has been merged with/rebased against the head of its merge target.
• There are no unexpected formatting changes, superfluous debug logs, or commented-out code.
• There are no circuit changes, OR a cryptographer has been assigned for review.
• New functions, classes, etc. have been documented according to the doxygen comment format. Classes and structs must have @brief describing the intended functionality.
• If existing code has been modified, such documentation has been added or updated.
• No superfluous include directives have been added.
• I have linked to any issue(s) it resolves.
• I'm happy for the PR to be merged at the reviewer's next convenience.