All event handlers inherit from event triggers

[tgberkeley]

All Submissions:

• Have you followed the guidelines stated in CONTRIBUTING.md file?
• Have you checked to ensure there aren't any other open Pull Requests for the desired changed?

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

New Feature Submission:

• Does your submission pass the tests?
• Have you linted your code locally prior to submission?

Changes To Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully ran tests with your changes locally?

After these steps, you're ready to open a pull request.

a. Give a descriptive title to your PR.

b. Describe your changes.

c. Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such).

[masenf]

i think this logic should go in Component.render itself. since the _rename_props attribute is defined on Component, it wouldn't really make sense to be able to set _rename_props, but then not have it work until the downstream component overrides render.

[tgberkeley]

added

[masenf]

Suggested change

	for ix, prop in enumerate(render_dict["props"]):
	# fast path
	if not self._rename_props:
	return
	for ix, prop in enumerate(render_dict["props"]):

[tgberkeley]

changed

[masenf]

Why twice?

[tgberkeley]

removed this

[masenf]

approve, when CI passes