Random class_tracker_id for dynamic class

cloudpickle generates random uuids to track dynamic classes, and those random uuids are added to outputs. For example, if there is a class serialized by value, the following lines are found with pickletools.dis

```
571: s SETITEM
572: \x8c SHORT_BINUNICODE 'fa5abda803d644e0bdcfdffec5c8f8d6'
606: \x94 MEMOIZE (as 56)
```

This string comes from `class_tracker_id` in cloudpickle and makes binary outputs different even though there is no code change.

Can random ids be replaced with deterministic ids, say a sequential number, for `class_tracker_id`?

This could be part of existing https://github.com/cloudpipe/cloudpickle/issues/453

Read issue 453 alongside the class_tracker_id generation path, then reproduce the example by serializing a dynamic class and inspecting the result with pickletools.dis. Compare repeated outputs and define whether deterministic IDs must remain stable across runs; done means equivalent serializations no longer contain random tracker IDs.

Written by the indexing model from the issue text.