Allow displaying children on Chrono node subview

[CarolineDenis]

Fixes #6086

Added a filterChronostrat param to specify_rows so that Chronostrats are only filtered when using the age picklist.

A potentially cleaner way to do this could be to pass an advancedFilter to fetchRows so that the filters we need (

specify7/specifyweb/specify/api.py

Lines 1018 to 1022 in 4fb34be

	filters.update({
	'startperiod__isnull': False,
	'endperiod__isnull': False,
	'startperiod__gte': F('endperiod')
	})

) can be passed directly from the frontend but I don't think it supports F expressions and so we would need a prop anyway. I figure this solution should suffice until there's a requirement for more flexible advancedFilters.

specify7/specifyweb/frontend/js_src/lib/components/PickLists/fetch.ts

Lines 157 to 167 in 36f7a7e

	return fetchRows(tableName as keyof Tables, {
	limit,
	fields: { [fieldName]: ['string', 'number', 'boolean', 'null'] },
	distinct: true,
	domainFilter: true,
	}).then((rows) =>
	rows
	.map((row) => row[fieldName] ?? '')
	.map((value) => ({ value, title: value }))
	);
	}

Checklist

• Self-review the PR after opening it to make sure the changes look good and
  self-explanatory (or properly documented)
• Add relevant issue to release milestone

Testing instructions

• Go to the chronostratigraphy tree
• Select a node and add a child
• Fill out required fields and save
• Select the parent node and click Edit
• Verify that the child node does appear under the Child Nodes subview
• Re-test Add valid chronostrat filter to geo_time relativeage and paleocontext queries #5411

[emenslin]

• Verify that the child node does appear under the Child Nodes subview
• Re-test #5411

Looks good

[pashiav]

• Verify that the child node does appear under the Child Nodes subview
• Re-test #5411

---

Looks good!