Adopt terms from Storage spec

[inexorabletash]

Nominally, replace "origin" with "storage key". But practically speaking:

• Associate a lock manager with a storage bottle
• Acquire a bottle from an environment, a manager from the bottle, and associate locks/requests with a manager

Some references to "storage bucket" are retained in prose where it seems to add value and is more correct than "origin".

Fixes #74

---

Preview | Diff

---

Preview | Diff

[inexorabletash]

@asutherland, @saschanaz, @mkruisselbrink - I'd appreciate your feedback here.

[inexorabletash]

The text "There is an equivalence between the following..." and associated Issue may be removable now.

[saschanaz]

Replace lock set and request queue associations with an origin with a lock manager instead

This better matches the current Gecko implementation, can we do it in a separate PR to make this one shorter?

[inexorabletash]

Replace lock set and request queue associations with an origin with a lock manager instead

This better matches the current Gecko implementation, can we do it in a separate PR to make this one shorter?

SGTM!

[saschanaz]

Cool, are you willing to do it or should I go ahead?

[inexorabletash]

Cool, are you willing to do it or should I go ahead?

I'm sure you'll get to it before I will!

[inexorabletash]

FYI, c/o a bunch of refactorings (thanks @saschanaz for PRs and reviews!) this PR is now a much more minimal change. I haven't actually updated any of the relevant parts about bottles/buckets/etc based on discussion above, though.

ObSeuss:

[saschanaz]

I need to get more familiar with the storage spec to fully understand this one, so for now I think @annevk is still the best person to review this.

[inexorabletash]

Updated - @saschanaz take a look?