visually identify dependencies that come from 'draft'

[jeffeaton]

A small feature suggestion if it is feasible: when using orderly_develop_start(use_draft = "newer"), it would be useful to visually identify which of the dependencies that get copied in are from the drafts/ folder in the console output below:

> orderly::orderly_develop_start(use_draft = "newer")
[ name       ]  mwi_data_programme
[ depends    ]  mwi_data_areas@20200929-213435-8f7790a3:mwi_areas.geojson -> depends/mwi_areas.geojson
[ ...        ]  mwi_data_facility@20210719-171136-64a44be1:mwi_facility_master.csv -> depends/mwi_facility_master.csv
[ ...        ]  mwi_raw_dhamis-obs@20220111-090058-de1b3284:dhamis_cumulative_art.csv.gz -> depends/dhamis_cumulative_art.csv.gz
[ ...        ]  mwi_raw_dhamis-obs@20220111-090058-de1b3284:dhamis_quarterly_art.csv.gz -> depends/dhamis_quarterly_art.csv.gz
[ ...        ]  mwi_raw_dhamis-obs@20220111-090058-de1b3284:dhamis_anc_testing.csv.gz -> depends/dhamis_anc_testing.csv.gz
[ ...        ]  mwi_raw_datim-obs@20220110-155454-2713c501:datim_art_facility_fine.csv.gz -> depends/datim_art_facility_fine.csv.gz

For example, an * at the start of the line, or something like that.

Thanks,
Jeff