Adapt build_and_upload_schemas CI job to new schema format

[webmaster128]

With the changes in 1.1.0, the full API is in one file. We can show this by getting rid of all the .tar.gz logic in the CI config:

      - run:
          name: Build and run schema generator for packages
          command: |
            for S in ./packages/*/examples/schema.rs
            do
              P=$(dirname $S)/..
              echo "Generating schema for $P ..."
              (cd $P && cargo schema --locked && tar -zcf ~/project/schemas/$(basename $(pwd))_schema.tar.gz ./schema)
            done
      - run:
          name: Build and run schema generator for contracts
          command: |
            for C in ./contracts/*/
            do
              echo "Generating schema for $C ..."
              (cd $C && cargo schema --locked && tar -zcf ~/project/schemas/$(basename $(pwd))_schema.tar.gz ./schema)
            done

Uploading a single .json per contract would be much nicer.

[ethanfrey]

Uploading a single .json per contract would be much nicer.

Yes, excited for one wasm and one json per contract.

[uint]

We cannot do this with packages since they don't have InstantiateMsgs. The new schema solution I intended for full contracts, not packages. Do we need to consider packages as well?

Or maybe we just want to stop generating schemas for packages? All those types will appear in the schema generated by end contracts anyway.

[uint]

I'll also note I doubt something like ts-codegen can do anything useful with an arbitrary package.

[webmaster128]

We cannot do this with packages since they don't have InstantiateMsgs. The new schema solution I intended for full contracts, not packages. Do we need to consider packages as well?

Good point. Then let's keep packages unchanged. For them the more primitive schema per type is probably still nice to have a look during development.