Describe the solution you'd like
Currently, to see the outcomes of ut.expect... one needs to create unit test package spec, unit test body and invoke the ut.run.
For some very simple (basic) test cases it would be hugely beneficial to allow invocation of expectations as it is possible in groovy.
For example, groovy allows for one-line asserts in groovy console:

def strArray = new String[3]
assert strArray instanceof String[]
strArray[0] = 'mrhaki'
strArray.putAt(1, 'Groovy')  // New syntax.
strArray[2] = 'Java'
 
assert 'mrhaki' == strArray.getAt(0)  // Just another way to get a value.

It would be great to be able to invoke utPSLQL expecations in similar way from SQLPlus or any other SQL console, example:

exec ut.expect(1).to_equal(2);

Additional context
When running outside of utPLSQL test-run, expectations should provide outputs straight to screen.
When running within utPSLQL test-run, they should provide outputs as they do today (to be consumed by reporters)