Tombstoning a stream leaves its natural key behind (JasperFx 2.100 NaturalKeyCompliance) #522

JasperFx 2.100.0's shared NaturalKeyCompliance adds two facts that Fisher fails, each with DuplicateNaturalKeyException:

• a_tombstoned_streams_natural_key_can_be_claimed_by_a_new_stream
• under_conjoined_tenancy_a_tombstoned_natural_key_can_be_claimed_and_other_tenants_keep_theirs

Tombstoning a stream leaves its fi_natural_key_* row behind, so a new stream cannot claim the key.

Done when

• Tombstoning a stream frees its natural key. Under conjoined tenancy only that tenant's key goes; other tenants keep theirs.
• Both facts pass on net9.0 and net10.0.

Found on the 1.28.0 release PR #521 (JasperFx 2.100.0, Weasel 9.49.0). That PR stays a version bump only, and the release (#517) waits on this. Tracked in the Stoat plan nov-5-releases.