Clarify support for rb_obj_info and why it's OK to not have it

Author: ivoanjo

ext/datadog_profiling_native_extension/extconf.rb

@@ -141,7 +141,9 @@ def skip_building_extension!(reason)
 # On Ruby 3.5, we can't ask the object_id from IMEMOs (https://github.com/ruby/ruby/pull/13347)
 $defs << "-DNO_IMEMO_OBJECT_ID" unless RUBY_VERSION < "3.5"
 
-# This symbol is only visible on certain Ruby versions: 2.6 to 3.2 and 3.4, but not 4.0
+# This symbol is exclusively visible on certain Ruby versions: 2.6 to 3.2, as well as 3.4 and 3.5-preview1 (but not 4.0)
+# It's only used to get extra information about an object when a failure happens, so it's a "very nice to have" but not
+# actually required for correct behavior of the profiler.
 $defs << "-DNO_RB_OBJ_INFO" if RUBY_VERSION.start_with?("2.5", "3.3", "4.0")
 
 # On older Rubies, rb_postponed_job_preregister/rb_postponed_job_trigger did not exist