Feat/core rework

[RLKRo]

Description

Breaking Changes

• All conditions (standard and slot) moved to chatsky.conditions
• All labels (standard) moved to chatsky.destinations
• All processing functions (slot) moved to chatsky.processing
• All responses (standard and slot) moved to chatsky.responses
• All conditions, destinations, processing functions, responses are now upper camel case
• script.core module moved to chatsky.core
• Pipeline moved to chatsky.core
• pipeline.service submodule moved to chatsky.core.service
• Added class Transition. TRANSITIONS is now a list of such objects instead of a dict. Destination, condition and priority are all fields of this class. Priority is now separate from node label
• Removed cnd.true and cnd.false. Condition field of Transition now accepts True and False literals. If condition field of Transition is not set, it defaults to True.
• Removed lbl.repeat renamed to dst.Current. Added dst.FromHistory to get labels from history past dst.Previous.
• Custom script functions now have to be subclassed from BaseScriptFunction. e.g. custom response function now have to be subclassed from BaseResponse.
• All keywords from chatsky.script.core.keywords moved to chatsky.core.script
• PRE_TRANSITIONS_PROCESSING renamed to PRE_TRANSITION
• PRE_RESPONSE_PROCESSING renamed to PRE_RESPONSE
• Removed chatsky.utils.turn_caching
• Turn id 0 is now reserved for start label. Actual turns start at id 1. Context has method init to init from a start label

Features

• RESPONSE can now be a string. It will be converted to Message(text=) automatically
• Custom functions do validation (e.g. response function can now return a string and it will be cast to Message)
• Current instance of Pipeline can now be accessed via Context.pipeline
• Added NodeLabel class to replace tuple node labels
• Added method Script.get_inherited_node to get a node that inherits global and local properties. ctx.current_node is obtained via this method
• Renamed response_comparer of check_happy_path to response_comparator, removed default comparators, removed context from signature; messages in happy_path can now be any of Message, dict, str; printout_enable flag renamed to printout and made False by default.
• Added ModifyResponse base processing class which allows modifying current node response.

Fixes

• Slot template filling now works for numerical slot names (e.g. slot_name="0")
• Slot Groups can now be initialized from a dictionary
• Exceptions in user functions are now properly handled:
  • response errors result in an empty message
  • processing errors are ignored
  • transition errors mark that specific transition as failed

Documentation

• Some improvements to basic conceptions user guide and global tutorial
• Added a tip on getting previous nodes to pre transition tutorial
• Removed responses.1_basics tutorial
• Slight improvements to web api interface tutorials

Devel

• Added log_event_catcher fixture to help test captured logs
• Added TYPE_CHECKING exclude from coverage; now only certain exception raises are excluded from coverage
• Removed run_interactive_mode. Just use pipeline.run().
• Removed Annotated values with pickle serializer/validators. Better to use field_validators/field_serializers to preserve model schema
• Added InitTypes for various BaseModels to indicate types that can be validated into that model
• Actor now doesn't have any parameters
• normalization utils replaced with pydantic validators
• An instance of Script can now be validated from a script dict (without the script field)
• Removed Context.cast. Use model_validate and model_validate_json instead.

Checklist

• [x] I have performed a self-review of the changes

To Consider

• Add tests (if functionality is changed)
• Update API reference / tutorials / guides
• Update CONTRIBUTING.md (if devel workflow is changed)
• Update .ignore files, scripts (such as lint), distribution manifest (if files are added/deleted)
• Search for references to changed entities in the codebase

[kudep]

Short review:

• [x] I think the method name should indicate that it's through CLI, for example, replace run with cli_run link
• [x] The name Current doesn't seem quite right, alternatives (This, Self, LoopBack)? link
• [x] A small suggestion: swap cnd and dst, so instead of Tr(dst="intro_node", cnd=cnd.ExactMatch("/start")), do Tr(cnd=cnd.ExactMatch("/start"), dst="intro_node")
• [x] I would remove text from the mandatory named arguments in Message
• [x] Since Pipeline is already in ctx, it’s better to use Pipeline from ctx rather than passing it as a service argument, here
• [x] It seems that cnd should always be a function; it's better to stick to this convention, here
• [x] This is pretty intense—a class within a class; maybe it could be simplified? here
• [x] Abbreviations are convenient, but when they are imported like this, it causes confusion and increases my heart rate, here

[RLKRo]

1. run is a method that runs it with the set interface. When using telegram interface pipeline.run is used as well. I could add comments explaining that pipeline.run starts up its interface which is CLI by default.
2. OK, I like dst.This. The only problem is that it would make less sense for LOCAL and GLOBAL than Current.
3. I'm assuming you mean in tutorials because order can be any. That suggestion makes sense.
4. If you're referring to the removed option to pass text as a first positional argument, that has been re-added here.
5. This is part of service update.
6. I did not understand this comment. Did you mean that Transition.cnd should never be a literal True or False? I don't see a reason to forbid this, but it is needed to have True by default.
7. I agree. I have a task to add a subclass of BaseProcessing that hides these parts making it easy to define a Processing that modifies response. I can implement that earlier and insert into the tutorial.
8. My thought process was that slot tutorial is not the first one user is going to see, so it's fine to introduce these convenient (hopefully) abbreviations at this point. But I can remove them.