Confusing when a got-away-with-it multiple snapshot stops getting away with it

Story:

- a user has a test where they are taking multiple snapshots that have the same name
- such as calling `toMatchDisk()` twice in one test
- the snapshots happen to be the same, so they get away with it
- something about the code being tested changes, and now the snapshots are different, so the test fails with this error message
- https://github.com/diffplug/selfie/blob/edb5f659760d5a0760810f5bedd89c44fa6a5b0f/jvm/selfie-lib/src/commonMain/kotlin/com/diffplug/selfie/guts/WriteTracker.kt#L70-L94
- [ ] The `hotToFix` is completely buried. It should come first!
- [ ] We should also advertise the `allow_multiple_equivalent_writes_to_one_location` property

報告されたエラーが組み立てられている jvm/selfie-lib/src/commonMain/kotlin/com/diffplug/selfie/guts/WriteTracker.kt の70-94行付近から始めてください。そこで hotToFix と allow_multiple_equivalent_writes_to_one_location がどのように表現されているかを確認してください。完了条件は、エラーが最初に hotToFix を提示し、そのプロパティを示すことです。

索引モデルが issue の本文から書いたものです。