Fixes #27261 - export-legacy should not be described as deprecated

[wbclark]

export-legacy method has different functionality from export and should not be described as deprecated

[theforeman-bot]

Issues: #27261

[akofink]

I'm fine with the change. @chris1984 were we planning to eventually remove the legacy export? I seem to remember some discussion around removing it so it's not confusing to users. I can see why we'd want to keep the old export around, though. For one, you don't need to be running hammer locally with Foreman for the legacy export.

[chris1984]

@akofink yeah there was talk about removing it but I am not sure where that went. Since I have not seen anything new around that topic I am fine with this change too since we are still supporting both ways. Marking as approved. Thanks, @wbclark 🍻

[wbclark]

@akofink @chris1984 Thank you for the quick turnaround on this one! Export-legacy does provide different functionality than the new export method, for example the new export method will fail when trying to export any CV version that contains non-RPM content, additionally the format of the exported content is different and some users have processes that are specifically dependent on that formatting. Therefore it's important to continue to support export-legacy.