fix package name and update version

[nioanto]

Testing the changes

• I tested the changes in this PR: YES

New package

• This new package conforms to the package requirements: YES

[ahesford]

In the future, please refrain from closing existing PRs and opening another to propose the same change. Not only does it create more noise and churn for project members, but it obfuscates the review history that led you to the current state of things.

Renames are generally painful but, when necessary, they require transitional packages with the old names to provide a proper upgrade path. Please grep through the repo for packages with descriptions containing the text "transitional dummy package" to see how that is done.

The commit message should be consistent with our usual style. Please look at the git history to ensure that you are consistent. Something like

xapps: update to 3.2.1, rename to xapp

would be appropriate.

[ahesford]

These lines should be wrapped at 80 characters.

[ahesford]

Don't kidnap packages from other maintainers, and also defer adoption until you've established a history of reliable package maintenance. Finally, ping the template maintainer when you touch a package. @the-maldridge

[nioanto]

Thank you for the feedback and guidance. I apologize for:

• Closing the original PR - I understand now that this creates unnecessary noise and loses review history
• Attempting to change the maintainer without permission - I've restored the original maintainer

I've now:

• Added the transitional dummy package for xapps
• Corrected hostmakedepends and makedepends
• Force-pushed to update this PR with the changes

I appreciate your patience as I learn the project's workflow and standards