[components] Move dagster-components test component lib to dagster_components.lib.test

[smackesey]

Summary & Motivation

Move the dagster-components test component library from dagster_components_tests.lib to dagster_components.lib.test. This lets us simplify entry point loading code (eliminate call to ensure_dagster_components_tests_import) and also ensures these components are accessible whether from a published dagster-components or local (we don't include our test packages in published distributions as a rule)

How I Tested These Changes

Existing test suite.

[smackesey]

• [components] Move global options to subcommands #26640
• [components] Change CLI from verb-noun to noun-verb #26623
• [components] Make dg generate code-location --use-editable-dagster include all dagster libs #26612
• [components] Move dagster-components test component lib to dagster_components.lib.test #26611 👈 (View in Graphite)
• [components] Add --rebuild-component-registry option, --skip-venv option, build cache on code loc construction #26591
• [components] Expose generation CLI params in dagster-dg #26478
• [components] Make dagster-dg help messages include parent options #26590
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[schrockn]

also ensures these components are accessible whether from a published dagster-components

Why is this desirable?

[smackesey]

Why is this desirable?

It is useful for testing. Currently there are some annoyances with some tests that construct a code location without an editable install, and I think this will prove useful in manual testing in the future.

But the primary reason for this is to simplify the entry point loading code path by removing the need to check for the separate package dagster_components_tests.

[schrockn]

Per discussion not sure this is where we end up landing, but it is incrementally better.

[schrockn]

Per discussion the longer term solution is to publish a standalone test package.