refactor(profiling): clarify init order in TaskInfo

Author: KowalskiThomas

ddtrace/internal/datadog/profiling/stack_v2/echion/echion/tasks.h

@@ -182,22 +182,21 @@ class TaskInfo
     PyObject* origin = NULL;
     PyObject* loop = NULL;
 
-    GenInfo::Ptr coro = nullptr;
-
     StringTable::Key name;
+    bool is_on_cpu = false;
+    GenInfo::Ptr coro = nullptr;
 
     // Information to reconstruct the async stack as best as we can
     TaskInfo::Ptr waiter = nullptr;
-    bool is_on_cpu = false;
 
     [[nodiscard]] static Result<TaskInfo::Ptr> create(TaskObj*);
     TaskInfo(PyObject* origin, PyObject* loop, GenInfo::Ptr coro, StringTable::Key name, TaskInfo::Ptr waiter)
       : origin(origin)
       , loop(loop)
-      , coro(std::move(coro))
       , name(name)
+      , is_on_cpu(coro && coro->is_running)
+      , coro(std::move(coro))
       , waiter(std::move(waiter))
-      , is_on_cpu(this->coro && this->coro->is_running)
     {
     }