[REFACTOR] Transition VisitAttrs to new reflection mechanism in tir/ir_builder/meta_schedule

[tqchen]

This PR transitions VisitAttrs to new reflection mechansim in the following components: tir, ir_builder, meta_schedule

[LeiWang1999]

Curious to learn why we need to refactor this part, and how we can reuse part of the parent class's reflect methods.

class SwizzledLayoutNode: LayoutNode {
...
}


# old code with AttrVisitor 
void LayoutNode::VisitAttrs(AttrVisitor *v) {
  v->Visit("input_size", &input_size_);
  v->Visit("forward_index", &forward_index_);
}

void SwizzledLayoutNode::VisitAttrs(tvm::AttrVisitor *v) {
  LayoutNode::VisitAttrs(v);
}

# new code
void LayoutNode::RegisterReflection() {
  namespace refl = tvm::ffi::reflection;
  refl::ObjectDef<LayoutNode>()
      .def_ro("input_size", &LayoutNode::input_size)
      .def_ro("forward_index", &LayoutNode::forward_index);
}

void SwizzledLayoutNode::RegisterReflection() {
  namespace refl = tvm::ffi::reflection;
   ?
}

[tqchen]

The new reflection mechanism would make the field access from python faster (about 10x) because we diretly access the address.

In the new code , you just need to do

void SwizzledLayoutNode::RegisterReflection() {
  namespace refl = tvm::ffi::reflection;
   // still need for parent relation to hold, but thats it
  refl::ObjectDef<SwizzledLayoutNode>();

}```