Tests for where overrides in __array_ufunc__

[mhvk]

This pull request is a short follow-up on #14590 to add (1) a test for Quantity that if one passes a quantity in where, it will raise a TypeError (in numpy >=1.25; before the unit is simply ignored); and (2) increase coverage for np.fix with an out argument.

cc @byrdie, @pllim

[github-actions]

Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.

• Do the proposed changes actually accomplish desired goals?
• Do the proposed changes follow the Astropy coding guidelines?
• Are tests added/updated as required? If so, do they follow the Astropy testing guidelines?
• Are docs added/updated as required? If so, do they follow the Astropy documentation guidelines?
• Is rebase and/or squash necessary? If so, please provide the author with appropriate instructions. Also see "When to rebase and squash commits".
• Did the CI pass? If no, are the failures related? If you need to run daily and weekly cron jobs as part of the PR, please apply the "Extra CI" label. Codestyle issues can be fixed by the bot.
• Is a change log needed? If yes, did the change log check pass? If no, add the "no-changelog-entry-needed" label. If this is a manual backport, use the "skip-changelog-checks" label unless special changelog handling is necessary.
• Is this a big PR that makes a "What's new?" entry worthwhile and if so, is (1) a "what's new" entry included in this PR and (2) the "whatsnew-needed" label applied?
• Is a milestone set? Milestone must be set but we cannot check for it on Actions; do not let the green checkmark fool you.
• At the time of adding the milestone, if the milestone set requires a backport to release branch(es), apply the appropriate "backport-X.Y.x" label(s) before merge.

[pllim]

RTD failure is unrelated.

[pllim]

Better coverage is always 👍 from me. Thanks!

I'll approve but give @byrdie a chance to review.

[byrdie]

Looks good to me, just a few ideas for minor improvements

[byrdie]

should we use the match= keyword here?

Suggested change

	with pytest.raises(TypeError):
	with pytest.raises(TypeError, match=r"Cannot cast array data from .* to .* according to the rule .*"):

[mhvk]

Yes, good idea, though I get a different error on numpy-dev (which I'll use...):

TypeError: operand type(s) all returned NotImplemented from __array_ufunc__(<ufunc 'add'>, '__call__', array([1., 1.]), array([1., 1.]), out=(array([1., 1.]),), where=<Quantity [ True,  True] m>): 'ndarray', 'ndarray', 'ndarray'

[pllim]

Do the different messages have anything in common that we can use some regex? If not, I guess we don't have to include "match".

[byrdie]

I think I must've been using the wrong version of numpy since @mhvk's version is correct.

[mhvk]

OK, adjusted. Will merge once tests pass. Thanks!