Performance analysis for gpu macro removal

Summary

The performance impact of removing the gpu macros used to stub the implementations of the GPU specific methods in CPU builds should be quickly tested to ensure that it doesn't create major performance regressions.

Use cases/Detailed description

Removing the macros will make it easier to port the accelerator layer to new targets, as it will be more clear which methods are implemented where based on the CMake inputs, instead of having the rather cryptic macros defined for it in one place. The macros are also not consistently used throughout the codebase.

We need to make sure that this doesn't create performance regressions because the function calls will no longer be inlined stubs in the CPU only build.

Impact

Avoid performance regressions for users