[ENH]: Add collection metadata to output collection to identify source attached function

[tanujnay112]

Description of changes

Summarize the changes made by this PR.

• Improvements & Bug fixes
  • As titled, add a collection metadata entry to all output collections. Using this, we prevent attaching functions to collections that were made as a result of functions.
• New functionality
  • ...

Test plan

How are these changes tested?

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Migration plan

Are there any migrations, or any forwards/backwards compatibility changes needed in order to make sure this change deploys reliably?

Observability plan

What is the plan to instrument and monitor this change?

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs section?

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[tanujnay112]

• [ENH]: Skip caching for output collections in frontend #5956
• [ENH]: Add collection metadata to output collection to identify source attached function #5955 👈 (View in Graphite)
• main

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

[propel-code-bot]

Add metadata flag to output collections and block function chaining

The PR introduces metadata tagging for attached-function output collections and uses that marker to prevent attaching another function to the same collection. It also wires the new error through the coordinator, updates constants, and adds regression coverage in Go and Python tests to validate the new guard.

Key Changes

• Set common.SourceAttachedFunctionIDKey metadata on output collections created in FinishCreateAttachedFunction
• Add guard in Coordinator.AttachFunction to return common.ErrCannotAttachToOutputCollection when the input collection carries the output metadata
• Expose the new ErrCannotAttachToOutputCollection constant in go/pkg/common/errors.go and go/pkg/common/constants.go
• Extend coordinator_test.go and chromadb/test/distributed/test_task_api.py with scenarios covering the new restriction

Affected Areas

• go/pkg/sysdb/coordinator/task.go
• go/pkg/sysdb/coordinator/coordinator_test.go
• chromadb/test/distributed/test_task_api.py
• go/pkg/common/errors.go
• go/pkg/common/constants.go

This summary was automatically generated by @propel-code-bot

[rescrv]

Which reads better:

• "source attached function id"
• "attached function id source"