General Procedure to update @joystream/types for a new runtime

Updating @joystream/types package

Outlined below are steps we need to take update @joystream/types package for a new runtime.

• Bump the package version
• Update the package.json dependencies of dependent packages in the monorepo to use the new version of @joystream/types
• Identify the version of @polkadot/api (keying, types, util, util-crypto) that matches with the new version of substrate being used in the runtime and update all packages in the monorepo, as well as the root package.json 'resolutions' with these versions.
• Identify new public types introduced in the runtime, or modified existing types.
  • by examining runtime code / code diff
  • by running a basic script to connect to the joystream-node with the new runtime and looking at warnings and/or errors about Unknown types.
    yarn workspace api-scripts status
api-scripts might need its dependencies updated before it works with new runtime
• Identify public types and modules removed from the runtime compared with prior version.
• Update the types package by defining the new types, updating existing ones if necessary, and removing unused types.
• New polkadot api version might have API changes, and the types package will need to be updated accordingly. For example some core type names might have changed like (AccountId --> Address)
• Running the generate:all script in the @joystream/types package to generate augment codec files
• Running build script to ensure build works. (linting and formatting also goes without saying)

Its possible to use the hosted polkadot apps by pointing it to our node, and injecting the types definition file types/augment/all/def.json to test basic functionality (functionality common to substrate and joystream)
This will work reasonably well if the version of polkadot and api and types are compatible with our version of substrate. For olympia where we have updated to v2.0.0 of substrate I think the api should be stable enough that it should work)

Start with the @joystream/types package and the root and dependent package.json files, then review the runtime code or diff for public type changes. Run yarn workspace api-scripts status against the new runtime, followed by the package's generate:all and build scripts. Done means the procedure documents dependency updates, type additions or removals, generated augment files, and successful builds.