[1.9] Update evaluation id logic to be in sync with tick ids

[OwenKephart]

Summary & Motivation

When running in user-code mode, evaluation ids are always based off of the tick id. This prevents us from having to deserialize the AssetDaemonCursor server side, and just in general is an easier way of producing monotonically increasing integers across multiple values.

In general, the tick id is guaranteed to be strictly larger than the AssetDaemonCursor value, as the daemon cursor (unless manually edited) cannot increase without a new tick being created. This means that it is safe to switch from daemon-mode to user-mode, but if you switch from user-mode back to daemon-mode, you could end up with an evaluation id that was much smaller, with the end result being that new evaluation records you produce would have a lower evaluation_id than older ones, messing up the history.

This change makes it so that the daemon-mode id will stay in sync with the tick id, avoiding this issue.

How I Tested These Changes

Existing tests, with some small updates.

Changelog

NOCHANGELOG

[OwenKephart]

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

• [1.9] Update evaluation id logic to be in sync with tick ids #25269 👈
• [1.9] Add automation_condition to observable_source_asset #25344
• [1.9] Create default_automation_condition_sensor in Definitions object #25201
• [1.9] Update deprecation warnings for automation_condition, auto_materialize_policy, and freshness_policy #25208
• [1.9] Remove experimental warnings from AutomationCondition static constructors #25207
• [1.9] Promote hidden params to top-level args in AutomationConditionSensorDefinition #25206
• [1.9] Update default value of allow_backfills to True #25204
• Add executed_with_root_target condition to handle partial runs / failures #25253
• Add error for user code sensors with too many entities targeted #25215
• Add test demonstrating that we do not hit the RESOURCE_EXHAUSTED error above a given threshold #25214
• Propagate automation condition information through the UI for user code conditions #25211
• Export AutomationContext and AutomationResult #25210
• Store allow_backfills in the sensor metadata #25203
• Create backfill_in_progress AutomationCondition #25190
• [refactor] Move all operands into a single file #25187
• Remove description property, make names more descriptive #25186
• Simplify return types of static constructors for AutomationCondition #25184
• Add all_deps_blocking_checks_passed condition #25171
• Make existing conditions work with Asset Checks #25170
• master

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

Join @OwenKephart and the rest of your teammates on Graphite