Timer arguments in ThingsDB scope are not checked as expected

[joente]

Describe the bug
When using timer arguments like things as timer arguments for the @thingsdb scope, things go wrong as the system is unable to assign the values to a collection and thus is not able to handle changes to these values.

To Reproduce

See the following code:

   new_timer(datetime(), |id, arg1, arg2| {
        nil;
    }, [123, {}]);

Expected behavior
ThingsDB should raise an exception when trying to use variable like things in a scope other than the collection scope.

[joente]

Fixed (with tasks) in v1.1.0-rc0