[runwhen-local-feedback] upload - needs a cleanup option

[stewartshea]

Observation
When uploading configurations to RunWhen Platform, we have a --keep-uploaded and --keep-existing merge mode. I ran into a case where objects were moved from one namespace to another, or just removed from a namespace, and with keep-uploaded, those stale objects still exist.

Possible Suggestions
I'm not quite sure how we want to handle this case, but I would suspect that if the object was generated by workspace builder (and thus, in the manifest) we can have an option to clean it up. And if it's manually created in the platform (e.g. not in the manifest?) then it could be preserved under the --keep-existing option? I'm open to any ideas and thoughts on it.