Add RecordSpecification implementation to the metadata module

[iramiller]

Summary

Implement basic metadata structure for RecordSpecification

Example

The following example is taken from a migrated v39 contract specification.

    {
      "inputs": [
        {
          "hash": "Adv+huolGTKofYCR0dw5GHm/R7sUWOwF32XR8r8r9kDy4il5U/LApxOWYHb05jhK4+eY4YzRMRiWcxU3Lx0+Mw==",
          "name": "perform_input_checks",
          "type_name": "io.provenance.Common$BooleanResult"
        },
        {
          "hash": "Adv+huolGTKofYCR0dw5GHm/R7sUWOwF32XR8r8r9kDy4il5U/LApxOWYHb05jhK4+eY4YzRMRiWcxU3Lx0+Mw==",
          "name": "additional_parties",
          "type_name": "io.provenance.loan.LoanProtos$PartiesList"
        }
      ],
      "name": "additional_parties",
      "responsible_party": "PARTY_TYPE_ORIGINATOR",
      "result_type": "DEFINITION_TYPE_PROPOSED",
      "specification_id": "contractspec1qvfha8nex5j0qeshr9uvsmv5um3q7sghss",
      "type_name": "io.provenance.loan.LoanProtos$PartiesList"
    },

Problem Definition

• Create proto message for RecordSpecification with appropriate identifiers and structure. Record Specifications are based on ConsiderationSpecs. The ID for a RecordSpecification should be a MetadataAddress (see Add support for RecordSpecification identifiers to the metadata address class. #58)
• Implement ValidateBasic for object
• Add NewRecordSpecification functions for creating an instance of [Object]
• Create test suite to cover basic validation logic
• Implement appropriate Stringer interface method, add test case
• Use associated specification keeper file for state read/write methods.
  • Get/Set/Remove methods for object in state store (include events and instrumentation publishing). Ensure remove method fails if there are any existing references to object. Update any indexes that might be useful for rapidly querying/accessing data for queries. Example: all scopes with a given value_owner
  • Stateful validation of object (pull existing, verify any updates are allowed, etc)
• Wire up msg_server and query_server endpoints to new keeper methods.

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned