fix: Improve error message for `SQLitePersister`

[zilto]

I always forget about calling .initialize() on the persister to create tables and that's the error I get:

  File .../assistant.py", line 86, in build_assistant
    .build()
     ^^^^^^^
  File ".../burr/telemetry.py", line 276, in wrapped_fn
    return call_fn(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File ".../application.py", line 2333, in build
    self._load_from_persister()
  File ".../burr/core/application.py", line 2262, in _load_from_persister
    load_result = self.initializer.load(_partition_key, _app_id, _sequence_id)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ".../burr/core/persistence.py", line 242, in load
    cursor.execute(
sqlite3.OperationalError: no such table: burr_state

Notes:

• it's a bit odd that the stack trace bounces between user code -> burr.telemetry -> user code -> burr.core.persistence
• could catch the uninitialized persister at ApplicationBuilder().with_state_persistence(...) instead of ApplicationBuilder().build(). (seems like a unlikely pattern to pass the persister then initialize it later)
• error message should say RuntimeError: Uninitialized persister. Make sure to call .initialize() before passing it to the ApplicationBuilder

[ghost]

@zilto can I take it up?

[zilto]

@arpitgupta-it Yes, you can work on it! Do you have any question? The goal is to catch more explicitly the missing table when calling self.initializer.load(...) and raise an appropriate error message

[ghost]

I just raised a PR. Please review if it looks good to approve or any changes.

[skrawcz]

@arpitgupta-it thanks I just added comments. We need to extend it to cover all persisters and maintain backwards compatibility with custom persisters people may have written.