Enable integration test workflow to communicate failure

[mfisher87]

Resolves #737

I don't have free time to debug the actual failures. Just getting the tests to fail loudly was a headache 😆 At a glance, I see a couple problems:

• We have some assertions at the module level that look like they should be set up in fixtures
• We're using unittest assert functions, so pytest is providing very poor error messages

[mfisher87]

Returned to draft; it was failing loudly in Act, but looks like still failing silently in GHA.

[betolink]

Thanks for noticing, I don't know when we started to exclude the integration tests!

[betolink]

Is there any reason not to merge? if the tests fail we should fix them. Maybe we need to visit the option to define a few popular datasets per DAAC instead of using random samples because some of them fail.

[mfisher87]

I think at minimum we need to update the fixture that allows 10% failure to communicate clearly that it was invoked before merging this one. Since it's a lot of work to rework the tests to remove that rule, this seems like a reasonable step. I'll try and take a look at that soon.