examples: general review and restructuring of examples

[karel-rehor]

Use Case

Examples should be organized to guide new and experienced users in how best to start with and then use the library with more advanced features. Examples, or new user examples at least, should also probably be self contained without dependencies on other examples having been run. For example a query example should not depend on the earlier run of a write example.

This is just a suggestion to

1. Document current examples
2. Reorganize/rename them
3. Ensure that they are sane for introductory user accounts with limited assets
4. Introduce one or two self-contained getting started ones

Expected behavior

That when using a initial user account, which will have limited assets, each example can be used and that an example will not push the account to exceed those limits.

That introductory examples should be self-contained, without depending on another example to prepare the state of the database.

Actual behavior

When running Examples/cloud_dedicated_query.py the example fails with the following error.

pyarrow.lib.ArrowInvalid: Flight returned invalid argument error, with message: bucket "flight2" not found. gRPC client debug context: UNKNOWN:Error received from peer ipv4:34.196.233.7:443 {created_time:"2024-04-05T10:59:19.006603056+02:00", grpc_status:3, grpc_message:"bucket \"flight2\" not found"}. Client context: IOError: Server never sent a data message. Detail: Internal

Or when running Examples/batching_example.py the example fails with the following...

The retriable error occurred during request. Reason: 'org fbb67cd4c8905be6 has exceeded limited_write plan limit'. Retry in 206s.

Additional info

No response