Added a read example with smoldot

[x3c41a]

1. Run bulletin
2. run node examples/smoldot_read.js

[x3c41a]

@bkontur I think it's a good practice to keep one package.json. I added package.json to one of ahm-dryrun subfolders and @seadanda suggested to stick to one package.json because:

• multiple package.json files may easily go out of sync and cause a "dependency drift",
• tools like tsconfig, jest, etc need to know which workspace they’re running in. Multiple package.json can lead to configs not being picked up correctly, working in one folder but not another.

Let's maybe revert back to a single package.json?

[seadanda]

Yea a single top level file was preferable for ahm-dryrun because we wanted to keep packages in sync and used the same frameworks etc everywhere, but sometimes you don't actually want that, and multiple package.jsons are fine (there are even some tools to manage that flow like npm workspaces/turborepo).

There are legit usecases for each, but I think that the simplest is best unless you need multiple

[bkontur]

Let's maybe revert back to a single package.json?

But we have just one examples/package.json.

Point of these examples is to use the same versions as simply as possible and run them as a part of CI. I don't see any reason to have multiple package.json and versions.

[x3c41a]

That's an old comment, it concerned the state of this PR (or related) when we had two package.json, now we have only one so it's already obsolete, I believe.