Tracker: TightCoder

[dk1a]

• Revisit TightCoder naming - decided to keep it
• consider moving it to a separate package (TightCoder doesn't really depend on store, except Slice.sol which is complicated) not worth it - it's useless outside of store, and separating it would be complicated (requires Slice and Memory as yet another package)
• add a typescript rendering utility in addition to pre-rendered solidity stuff making a generalized tight encoder is needlessly complicated; codegen was refactored to use typescript though
• (using the utility) try preallocate for all, encodePacked statics, and direct encode dynamics in
  store/ts/codegen/record.ts (see feat: v2 - add store, world and schema-type, cli table code generation #422 (comment)) making a generalized tight encoder is needlessly complicated; gas implications likely not significant; may be worth exploring again in the future
• Revisit _encodeToLocation in TightCoder (see feat: v2 - add store, world and schema-type, cli table code generation #422 (comment)) refactor(store): update tightcoder codegen, optimize TightCoder library #1210
• Remove sanity checks in TightCoder (see feat: v2 - add store, world and schema-type, cli table code generation #422 (comment))
• consider removing solidity stuff, keeping only the js utility (not sure, seems bad) making a generalized tight encoder is needlessly complicated

[dk1a]

Revisit TightCoder naming

some proposed alternatives from #387:
DataPack, DataPacker, BytePacker, BytesPacker, DataCoder, ByteCoder, Serializer

[alvrs]

closing this as since all todos are done