[24.0] Assign default data extension on discovered collection output

[mvdbeek]

Prevents #18383. To really close out #18383 we should probably add a migration that makes the column non-nullable and fills existing nulls with the "data" string.

How to test the changes?

(Select all options that apply)

• I've included appropriate automated tests.
• This is a refactoring of components with existing test coverage.
• Instructions for manual testing are as follows:
  1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

• I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

[bernt-matthias]

One could also think about making this a linter error. Not sure if this one .. or a new linter would be better.

[mvdbeek]

it is a warning, but its not perfect since it doesn't cover galaxy.json

[mvdbeek]

test failures are unrelated

[bernt-matthias]

It actually has rudimentary galaxy.json support via _has_tool_provided_metadata. But the call to the function might need to be moved. And the check isn't perfect (and probably can't be).