[PLT-1421]Build test-py-pi for a dev merge even if tests fail

[vbrodsky]

Description

1. Need to make sure we build our library on test-pypi for ALL dev merges
2. Will tell QA to use a different command in their collab to pull it test-pypi. The command they use now will not work

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Document change (fix typo or modifying any markdown files, code comments or anything in the examples folder only)

All Submissions

• Have you followed the guidelines in our Contributing document?
• Have you provided a description?
• Are your changes properly formatted?

New Feature Submissions

• Does your submission pass tests?
• Have you added thorough tests for your new feature?
• Have you commented your code, particularly in hard-to-understand areas?
• Have you added a Docstring?

Changes to Core Features

• Have you written new tests for your core changes, as applicable?
• Have you successfully run tests with your changes locally?
• Have you updated any code comments, as applicable?

[adrian-chang]

needs: ['path-filter']
don't make it depend on tests

[adrian-chang]

the other change (if etc. continue on error isn't needed)

[adrian-chang]

Also, make test-container only depend on needs: ['path-filter'] and not on tests