Mechanism to populate treetracker.tree from treetracker.capture

Since only some projects have used a code coming from the App within the `treetracker.public.trees.note` field to identify the first appearance of a tree other orgs and users need to be able to select captures and turn them into tree records. (capture->tree) in order to follow the new domain model and activate the capture matching tool etc.
This would need a small UI but could/should be part of the verification process.

Start by reviewing the admin panel's verification flow and how capture and tree records are represented. Define how a user selects captures and turns them into tree records, then verify that the flow supports the capture matching tool and the new domain model.

Written by the indexing model from the issue text.