Remove the `wheel` build (backend) dependency, since it is not necessary (new versions of setuptools don't need it, old versions pull it automatically).

Remove the `build` runtime dependency. The `build` package is a frontend used during in development workflows, and it neither needs to be installed when installing the package from a wheel, nor it needs to be kept once it's installed.

_ta_func_unst_ids was built with enumerate() over the TA-Lib 0.4.0 names.
TA-Lib C 0.6.0 inserted TA_FUNC_UNST_IMI at slot 12, so every id from there
up mis-targets: set_unstable_period('RSI') sets PLUS_DM's unstable period,
'MAMA' sets KAMA's, and 'ALL' sets T3's alone. setup.py requires
ta-lib >= 0.6.1, so this affects every normal install.

Take the ids from lib.TA_FUNC_UNST_* instead. Cython reads the value of a
`cdef extern` const from the header at build time and ignores the literal
written in the .pxd, so one table is correct for every ta-lib release with
no version detection.

'ADXR', 'MFI' and 'STOCHRSI' remain accepted keys but are now no-ops that
emit a DeprecationWarning; TA-Lib C retired those slots. They are not
aliased to the inner ADX/RSI, which would turn a long-standing no-op into a
call with side effects on other functions.

In _ta_lib.pxd, fix the TA_FUNC_UNST_HD_PHASOR typo, drop the stale literal
values, and drop the enumerators that no longer exist.

The new test is behavioural on purpose: set and get look the id up in the
same table, so a wrong id round-trips perfectly.

Verified against ta-lib C 0.6.4, 0.7.1 and 0.8.1.

TA-Lib C 0.8.1 is now the minimum required version.

- Bind the 40 functions added since 0.7.1: 161 -> 201.
- MA_Type gains HMA, DISABLED, DEFAULT, ZLEMA and RMA; set_unstable_period()
  gains RMA, HA and RVI.
- generate_func.py / generate_stream.py: skip any declaration mentioning a
  TA_<FUNC>_Stream handle. The verb list it replaces missed _Value and _Clone,
  which 0.8.1 declares for every function.
- generate_func.py / generate_stream.py: a moving-average parameter not spelled
  exactly 'matype' -- KDJ's slowk_matype -- defaulted to SMA rather than to the
  function's own default, so func.KDJ and abstract.KDJ disagreed.
- abstract: ignore flag bits added after this wrapper was written instead of
  raising KeyError, and keep the -100/0/100 wording for candlesticks only
  (SUPERTREND's integer output is a trend direction).
- Building against an older ta-lib now fails at compile time; the import guard
  explains a stale extension.
- Tests: func and abstract must agree on all 201, and the stubs must parse and
  cover every function.

talib/_ta_lib.c is left untouched; it is refreshed at release time.

Claude-Session: https://claude.ai/code/session_01R8JMZAcnp5snoMjFd1HyMU

See 0.8.1 release notes:

(#388) API: the MetaStock variant when the MAType is EMA, DEMA or TEMA
is removed. Default behavior is unchanged. TA_SetCompatibility() and
TA_GetCompatibility() remain, so existing sources still compile and
link, but the setter now does nothing and the getter always answers
TA_COMPATIBILITY_DEFAULT. Moving forward TA-Lib no longer supports
"Compatibility Settings".