Support for codesigning Sparkle framework bundled in a plugin (or skip sparkle sign from automate)

[am-play]

Problem
I am deploying a Mac Catalyst app. The app bundles the Sparkle framework inside of a plugin, so the sparkle signing steps are looking in the wrong path for the Sparkle framework.

exported_app/SparkleTest.app/Contents/Frameworks/Sparkle.framework/AutoUpdate: No such file or directory

The framework in my app located at:

exported_app/SparkleTest.app/Contents/PlugIns/AppKitPlugin.bundle/Contents/Frameworks/Sparkle.framework/

Describe the solution you'd like

I am already signing the Sparkle framework using --deep flag in my xcode archive settings. I would like to be able to pass --skip-sparkle-steps to the automate command, currently I can only pass it directly to the export command.

Describe alternatives you've considered
Alternatively, being able to pass and arg (or env prop) for --sparkle-framework-path (relative to the exported .app file?)

Thanks,

Andrew