[API] New API call in the Execution Plan to log/trace the plan

[jjfumero]

Description

This patch extends the API with a new method to log/dump the operations enabled for the TornadoVM execution plan.

New methods:

plan.printTraceExecutionPlan();

String s = plan.getTraceExecutionPlan()

How to use it?

// Testing multiple functions to invoke the print logic plan later
executionPlan.withWarmUp() //
      .withDevice(device) //
      .withGridScheduler(grid) //
      .withThreadInfo() //
      .withProfiler(ProfilerMode.SILENT);

// When we call execute(), then it records the path 
executionPlan.execute();

Output:

Root
 -> withWarmUp 
 -> withDevice 
 -> withGridScheduler 
 -> withThreadInfo 
 -> withProfiler 

Problem description

n/a.

Backend/s tested

Mark the backends affected by this PR.

• OpenCL
• PTX
• SPIRV

OS tested

Mark the OS where this PR is tested.

• Linux
• OSx
• Windows

Did you check on FPGAs?

If it is applicable, check your changes on FPGAs.

• Yes
• No

How to test the new patch?

tornado-test -V --fast uk.ac.manchester.tornado.unittests.executor.TestExecutor#test05

make tests

[mikepapadim]

Do you think it makes sense to make the ExecutionPlan types records instead?

[jjfumero]

ExecutionPlanType cotains mutable fields and it extends another class, so we can't.

[stratika]

minor changes suggested, thanks for the PR.

[jjfumero]

Thank you @stratika , I refactored the classes.

[stratika]

Thank you @stratika , I refactored the classes.

perfect, I will do final testing before the approval.

[stratika]

Tested in Linux OS, all backends.