Added tier parameter to plugin RPC target BucketId

Changed sbroad vshard related traits and it's capabilities
about working with several vshard groups

- use RouteBuilder to register rpc endpoints (input and ouptut is raw
  bytes for now)
- use RequestBuilder to send RPC requests to other instances which are
  running a specified plugin.service (guarded by version)
    - supported routing by
        - explicit instance_id
        - replicaset_id
        - bucket_id
        - any available instance with given service
- use context::Context to extract information about request or add
  custom fields at runtime (middleware not yet implemented)

BREAKING CHANGE: "name" index in the _pico_index has changed:
previously it guarantees uniqueness for a pair of (space_id,
index_name). Now index name must be unique among the cluster.
So, all the global indexes for _pico tables were renamed.

godzie44 authored 11 months ago and Yaroslav Dynnikov committed 11 months ago

Introduce a plugin system for picodata cluster.
Plugin system contains:
- `picoplugin` crate with plugin interfaces.
This crate exposes plugin interfaces for user implementation and API
that used by picodata to interact with plugin as with a code from dynamic library.
- Support for plugin work cycle in picodata instance work cycle.
Picodata instance interacts with running plugin by `PluginManager`
component.
Typically, plugins react to events that occur in instance or whole cluster.
- New lua API with plugin CRUD actions.
    - pico.create_plugin - load a new plugin into picodata cluster
    - pico.remove_plugin - remove plugin from picodata cluster
    - pico.update_plugin_config - update plugin service configuration

Dmitry Rodionov authored 1 year ago and Yaroslav Dynnikov committed 1 year ago

This patch adds initiator field to most of the events. Initiator is
added to members of Op enum which do not contain it already (e g owner
in CreateUser serves as initiator). To me it is reasonable to remove
as_user from CaS/ACL checks because it matches initiator. But I decided
not to do this just yet.

Additionally I've mande small cleanup to UserMetadata to avoid need for
intermediate step in decoding when we first fetch tuple and then decode
it into model struct.

Close https://git.picodata.io/picodata/picodata/picodata/-/issues/433

This change allows for creators of corresponding objects to consequently have all privileges on them.

Rename space object type to table

Was changed in this commit:
https://git.picodata.io/picodata/picodata/picodata/-/commit/4b3b1650423e83724dc8915a0d5bb0c643c31a80

I believe this change was introduced by mistake (most probably because
of bulk rename)

The patch adds `password_min_length` parameter to `_pico_properties` space.
The parameter is taken into account in `pico.create_user` and 
`pico.change_password` lua functions.