Improve package publish UX for skeleton and create+publish flows

[AustinAbro321]

Is your feature request related to a problem? Please describe.

There are currently a few UX problems with publishing normal (non-skeleton) Zarf packages.

• A user running zarf package publish path/to/package may expect their package to be built and published. Instead a skeleton package will be published. We have seen multiple community members post that this behavior is confusing
• Users may want to publish and create a package in one step. This may be important if they have an extremely large package that is expensive to compress and decompress. It is possible to do this with zarf package create path/to/package --output=oci://registry, however this is not easy to discover. The typical user would expect this functionality in zarf package publish path/to/package

The solution should be done as follows

1. Deprecate zarf package publish path/to/dir by replacing it with a new command zarf package publish skeleton path/to/dir. After a year has passed zarf package publish path/to/dir should create and publish a normal package.
2. Once the above has been fully implemented, deprecate the --output=oci://registry functionality from create and warn users to switch to zarf package publish. After a year remove the --output functionality.