fix(craftingschema): move annotations to spec

[Piskoo]

This PRs fixes the placement of attestation-level annotations in the v2 schema moving them back to spec like in v1 schema.

apiVersion: chainloop.dev/v1
kind: Contract
metadata:
  name: chainloop-contract
spec:
  annotations:
    - name: environment
    # value is empty so environment will have to be specified during attestation process

[migmartri]

does this work by only providing the name not the value, so the value is recovered at runtime?

[Piskoo]

Yes, the annotation value is required if it wasn't provided in the contract

$ cl att push
WRN API contacted in insecure mode
ERR annotations ["environment"] required