Reorder inheritance on span nodes

[hmstepanek]

Overview

Core tracing will be adding a bunch of logic to the span_event method which is called via super on inheriting classes before those inheriting classes add additional attributes. In order for the core tracing logic to work correctly, this inheritance call order has to be reversed; the inheriting classes must first add the attributes and THEN call super.

[github-actions]

✅MegaLinter analysis: Success

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ ACTION	actionlint	7		0	0	0.98s
✅ MARKDOWN	markdownlint	7	0	0	0	1.14s
✅ PYTHON	ruff	946	0	0	0	1.15s
✅ PYTHON	ruff-format	946	0	0	0	0.35s
✅ YAML	prettier	15	0	0	0	1.51s
✅ YAML	v8r	15		0	0	6.09s
✅ YAML	yamllint	15		0	0	0.63s

See detailed reports in MegaLinter artifacts

[codecov-commenter]

Codecov Report

❌ Patch coverage is 92.30769% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 71.38%. Comparing base (27f357c) to head (ec37cdc).

Files with missing lines	Patch %	Lines
newrelic/core/loop_node.py	33.33%	2 Missing ⚠️

❗ There is a different number of reports uploaded between BASE (27f357c) and HEAD (ec37cdc). Click for more details.

HEAD has 5 uploads less than BASE

Flag	BASE (27f357c)	HEAD (ec37cdc)
	6	1

Additional details and impacted files

@@                       Coverage Diff                        @@
##           develop-hybrid-core-tracing    #1539       +/-   ##
================================================================
- Coverage                        81.72%   71.38%   -10.35%     
================================================================
  Files                              207      207               
  Lines                            23909    23904        -5     
  Branches                          3789     3789               
================================================================
- Hits                             19540    17064     -2476     
- Misses                            3098     5302     +2204     
- Partials                          1271     1538      +267     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[lrafeei]

This is more of a general question: Originally, span_event() in each node class had "*args, **kwargs" as the signature but now they have the keyword arguments and the *args, **kwargs in their signature. All of these keyword arguments are the same and there is not a node class that uses something different/extra, so do we even need the "*args, **kwargs" part of the signature anymore?