"Age" field returns `CollectionObjectID`, should return useful information

[grantfitzsimmons]

Describe the bug

Currently, adding the "Age" field to a query creates a column displaying the CollectionObjectID. This identifier is likely unfamiliar to users and may cause confusion in the interface. This is not a catalog number (identifiable) or any other useful information.

To Reproduce

Steps to reproduce the behavior:

1. Build a "Collection Object" query in a paleo/invertpaleo/geology discipline's collection
2. Add the "Age" field to the query
3. Run the query
4. See that the Collection Object ID is all that is shown in the results

Expected behavior

Show the full range computed by the back end for each CO

• The backend currently search across 3 tables: relative age - absolute age and paleo context.
• Each value coming from those tables, if any, is transform into a start date and en end date.
• That new computed range is used to define which CO is returned or not.
• The column for the virtual field 'Age' in the query result should return that computed range.
• This could therefore be a different value for each line

Let say the user adds the age field in his mapping and use the range filter.
He enters the values 120 - 10 in his filter.
One CO in the db has those value for each age table once converted to range numbers:
Absolute age: 110 - 50
Relative age: 100 - 50
PaleoContext: 80 - 40
The maximum range for this CO is then defined to be 110 - 40.

==> This 110 - 40 should be the value displayed in the query result column

[grantfitzsimmons]

From @emenslin:

My immediate assumption was that when I searched the name that only the results with the matching name would appear. That doesn't have to be how it is, but since it is separate from the range filter that was what made the most sense to me. Including something like the range with the name like you suggested could also make sense but then at that point why would the name be separate from the range? I don't know, I think in general this feature is not very intuitive to the user especially with #5412 and even after looking at #5180 I still feel a bit confused.

This would do a lot to resolve this as well.

[CarolineDenis]

NOTES:
For future versions:
#6089
#6088