Feature/trigger in dataextensions

[tiller1010]

Description

Allows StaticPublishingTrigger to be added in DataExtensions

Manual testing steps

• Add a DataExtension to a DataObject without StaticPublishingTrigger
• Also add the SiteTreePublishingEngine extension to that DataObject
• Confirm the instances of the DataObject have their URLs queued to be cached when saved/published

Issues

Closes #211

Pull request checklist

• The target branch is correct
  • See picking the right version
• All commits are relevant to the purpose of the PR (e.g. no debug statements, unrelated refactoring, or arbitrary linting)
  • Small amounts of additional linting are usually okay, but if it makes it hard to concentrate on the relevant changes, ask for the unrelated changes to be reverted, and submitted as a separate PR.
• The commit messages follow our commit message guidelines
• The PR follows our contribution guidelines
• Code changes follow our coding conventions
• This change is covered with tests (or tests aren't necessary for this change)
• Any relevant User Help/Developer documentation is updated; for impactful changes, information is added to the changelog for the intended release
• CI is green

[GuySartorelli]

Can you please check all the boxes that apply in the PR checklist? That checklist is there so that you as the contributor can make sure you're doing things correctly before this gets reviewed. For example the commit message doesn't follow the guidelines.

[GuySartorelli]

LGTM, thanks for providing this improvement.
I'll fix up the commit message on merge.