chore: meta.yaml to accommodate numpy-base or numpy

[jharlow-intel]

adds USE_NUMPY_BASE toggle that defaults to true for internal meta.yaml

Plan is the recipe can support either or in the near-future.

Tried to be helpful and bump the version number, too

[ndgrigorian]

@jharlow-intel
It is still not clear to me, why do we need to keep numpy-base dependency?

For a fallback, it's clear what purpose it might serve, but I'm not sure I follow the issue with the wheels.

[jharlow-intel]

@jharlow-intel It is still not clear to me, why do we need to keep numpy-base dependency?

For a fallback, it's clear what purpose it might serve, but I'm not sure I follow the issue with the wheels.

For wheels, the ecosystem itself does not support non-root system packages(this is a big reason why conda was created in the first place, to make isolated environments that don't pollute system paths), so we pretty much have to continue ensuring we use Intel numpy for wheels in the meantime until we make some kind of workaround for that.

Maybe I'm misunderstanding what we can here, though

[jharlow-intel]

Debugging this so converting to draft

[jharlow-intel]

wheels builds are going to act a little funny because the jenkins CI logic isn't merged yet, but new CI logic was tested manually, this PR works.