fix(gatsby): make sure 404 and 500 pages inherit stateful status from original page

[pieh]

Description

With the way we have our 404 (and now 500) canonical pages setup (/404.html / /500.html) we clone page object from some conventional paths like (/404/) but we don't attach same isCreatedByStatefulCreatePages flag as original page. This required some workarounds (like skipping /404.html when decidiing which pages should no longer be there), but they had some of their own issue. Instead of that if we will guarantee same state on child page then pages cleanup for child page will be the same as parent page and this is what we want instead of workarounds.

[pieh]

We pass third arg (actionOptions) so that this check

gatsby/packages/gatsby/src/redux/actions/public.js

Lines 397 to 398 in 83396a5

	isCreatedByStatefulCreatePages:
	actionOptions?.traceId === `initial-createPagesStatefully`,

actually do something.

actionOptions are spread on CREATE_PAGE action itself -

gatsby/packages/gatsby/src/redux/actions/public.js

Lines 492 to 498 in 83396a5

	{
	...actionOptions,
	type: `CREATE_PAGE`,
	contextModified,
	plugin,
	payload: internalPage,
	},