add paginated partition key graphql fields to partitioned asset nodes

[prha]

Summary & Motivation

Add paginated partition materializations field on asset node graphql fields.

How I Tested These Changes

BK

[prha]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• remove partition view on asset events for non-sda assets #28941
• change UI to narrow asset events query #28903
• add paginated partition key graphql fields to partitioned asset nodes #28774 👈 (View in Graphite)
• add dynamic store connection APIs #28655
• partition key pagination APIs #28311
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

Deploy preview for dagit-core-storybook ready!

✅ Preview
https://dagit-core-storybook-jtz96hlz9-elementl.vercel.app
https://prha-graphql-partition-keys.core-storybook.dagster-docs.io

Built with commit dd30b2e.
This pull request is being automatically deployed with vercel-action

[graphite-app]

The order of these checks should be swapped to improve error handling. First check if not self._remote_node.is_partitioned: and return None, then check for the dynamic partitions loader.

The current implementation will raise an error about missing dynamic_partitions_loader even for non-partitioned assets, which is confusing since the loader isn't needed in that case. By checking partitioning first, you'll avoid unnecessary errors for non-partitioned assets.

Suggested change

	if not self._dynamic_partitions_loader:
	check.failed("dynamic_partitions_loader must be provided to get partition keys")
	if not self._remote_node.is_partitioned:
	return None
	if not self._remote_node.is_partitioned:
	return None
	if not self._dynamic_partitions_loader:
	check.failed("dynamic_partitions_loader must be provided to get partition keys")

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.