chore: Use agoric types

[sirtimid]

Closes #337

Since the types from @agoric packages are now exported we can remove our own definitions and let TS do its thing.

I left our Syscall related types since those are exported as any from agoric.

[socket-security]

Updated and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@agoric/swingset-liveslots@0.10.3-dev-3d64bee.0 🔁 npm/@agoric/swingset-liveslots@0.10.3-u18.0	None	0	850 kB	agoricbot
npm/@endo/common@1.2.9 🔁 npm/@endo/common@1.2.8	None	+2	91.1 kB	kriskowal
npm/@endo/exo@1.5.8 🔁 npm/@endo/exo@1.5.7	None	0	53.8 kB	kriskowal
npm/@endo/far@1.1.10 🔁 npm/@endo/far@1.1.9	None	+1	143 kB	kriskowal
npm/@endo/init@1.1.8 🔁 npm/@endo/init@1.1.7	None	0	31.8 kB	kriskowal
npm/@endo/lockdown@1.0.14 🔁 npm/@endo/lockdown@1.0.13	None	0	28.2 kB	kriskowal
npm/@endo/marshal@1.6.3 🔁 npm/@endo/marshal@1.6.2	None	0	174 kB	kriskowal
npm/@endo/nat@5.0.14 🔁 npm/@endo/nat@5.0.13	None	0	26.1 kB	kriskowal
npm/@endo/patterns@1.4.8 🔁 npm/@endo/patterns@1.4.7	None	0	233 kB	kriskowal
npm/@endo/stream@1.2.9 🔁 npm/@endo/stream@1.2.8	None	0	34.2 kB	kriskowal

🚮 Removed packages: npm/@fast-check/ava@1.2.1, npm/fast-check@3.23.2, npm/pure-rand@6.1.0, npm/ses@1.10.0

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Manifest confusion	npm/@agoric/swingset-liveslots@0.10.3-dev-3d64bee.0	Location: Package overview	packages/kernel/package.json	⚠︎

View full report↗︎

Next steps

What is manifest confusion?

This package has inconsistent metadata. This could be malicious or caused by an error when publishing the package.

Packages with inconsistent metadata may be corrupted or malicious.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/@agoric/swingset-liveslots@0.10.3-dev-3d64bee.0

[rekmarks]

LGTM!