Replace lzma with xz dependency

[wdconinc]

lzma (https://tukaani.org/lzma/) has been out of maintenance since 2008, and the developer indicates that "Users of LZMA Utils should move to XZ Utils" (https://tukaani.org/xz/). Because both lzma and xz are presenting themselves as liblzma there is a potential for confusion, and lzma can reasonably be indicated as deprecated.

The current dependents of lzma are:

$ spack dependents lzma 
angsd eagle kmod py-pyliblzma rpm srcml-identifier-getter-tool

• The package py-pyliblzma is proposed for removal in py-pyliblzma: remove python2 package #39399.
• This PR updates angsd, eagle, kmod, rpm, and srcml-identifier-getter-tool.
  • angsd, eagle, kmod, and srcml-identifier-getter-tool build fine with xz for both oldest and newest version in spack
    • angsd fails to link in an unrelated part of the code for other reasons since fixed (Fix for HTSlib linking issues (and HTSlib compilation for TravisCI) ANGSD/angsd#372), it would need a newer version of htslib and angsd but that's out of scope here.
  • rpm has supported xz 5.2.0 since 4.14, older than what is in spack (rpm-software-management/rpm@bec7592), but its lua dependency fails to download a required patch to provide a pkg-config file required by rpm because of a dead link, see lua: update pcfile patch #39403.

[spackbot-app]

Hi @wdconinc! I noticed that the following package(s) don't yet have maintainers:

• angsd
• kmod
• srcml-identifier-getter-tool

Are you interested in adopting any of these package(s)? If so, simply add the following to the package class:

    maintainers("wdconinc")

If not, could you contact the developers of this package and see if they are interested? You can quickly see who has worked on a package with spack blame:

$ spack blame angsd

Thank you for your help! Please don't add maintainers without their consent.

You don't have to be a Spack expert or package developer in order to be a "maintainer," it just gives us a list of users willing to review PRs or debug issues relating to this package. A package can have multiple maintainers; just add a list of GitHub handles of anyone who wants to volunteer.

[snehring]

eagle change should be fine.