[SYCL][Graph] Add support for handler-less graph submission

[mmichel11]

• Adds submit_graph_direct_with_event_impl and submit_graph_direct_without_event_impl to the ABI which invoke a handler-less path for graph submission for queue::ext_oneapi_graph and the free function execute_graph.
• Adjusts handler-less submit_direct utility to be more general: support submissions which may contain host task, move scheduler bypass logic to callback functor, and parameterize submission CGType.
• Extends graph test coverage to cover identified gaps: recording handler-less graph submission and host task cases with dependencies.

[slawekptak]

I think that checking MNoLastEventMode here works (as this is what the handler path does). One of my longer term goals for the handler-less path however, was to avoid using MNoLastEventMode synchronization flag. Instead of checking that flag, my plan was to rely on the LastEvent being set. If SchedulerBypass is true, then we just unset it, since the lower layers take care of the ordering. If it is false, then we have to set it, since the kernel submission to the scheduler requires ordering on the SYCL layer.
The MNoLastEventMode is still used in queue_impl::wait, which is generic, so this may be a subject to future changes. The current handler-less path however updates that flag only for compatibility with the handler path.
I think there are three cases here:

1. The LastEvent is set, then we simply add the dependency
2. The LastEvent is not set - we are in the No Last Event Mode - we have to insert the barrier
3. The LastEvent is not set - nothing was submitted to this queue yet - then we might use the MEmpty flag? But probably we have to move the MEmpty.store() to after this check.

Please let me know if this thinking makes sense and if it would be possible to replace the use of the MNoLastEventMode flag here.