semantic model: add interaction current slot state

[adrianbr]

"add context of all slots that have value at given conversation interaction"

[rudolfix]

is this query OK?

with slots as (SELECT distinct
        sender_id as conversation_id,
        _record_hash as slot_record_hash,
        s.name,
        case when s.value = 'None' then null else s.value end as value,
        case when name = 'requested_slot' then value else name end as slot_name_normalised,
        case when name = 'requested_slot' then 'requested_slot' else 'filled_slot' end as slot_action_normalised,
        timestamp
    FROM jupyter_extract_1_event.event_slot as s
    where sender_id = '11c55dc9-ad1e-459f-aa4a-d2df2d29e5ea')

1. case when s.value = 'None' then null else s.value end as value None should never happen :) maybe the old loads were buggy
2. where sender_id = '11c55dc9-ad1e-459f-aa4a-d2df2d29e5ea') looks like some debug code
3. it does not return any data no matter what I do with the effect that slots in views are always empty...

I think we mess up two things:

1. requested and filled slots as in active loop (form context)
2. a basic information that tells me all slot names and values at particular interaction id

[rudolfix]

achtung: action_restart resets all the slots https://rasa.com/docs/rasa/default-actions/#action_restart

[rudolfix]

I've limited the mechanism of matching fills and request to particular active loop of a given form. outside the form matching was meaningless.
looks like it works now
we need to write some tests...

[rudolfix]

we still lack a table that says which slots are set at a given conversation step. such table will be huge. we could use for example use pivot function from dbt_utils to get slots as columns.