Use cask tab to better identify installed casks

[apainintheneck]

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same change?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes? Here's an example.
• Have you successfully run brew style with your changes locally?
• Have you successfully run brew typecheck with your changes locally?
• Have you successfully run brew tests with your changes locally?

---

Fixes #17427
Fixes #17416

Previously we would identify installed casks by token derived from directories present in the caskroom directory. That was error prone when the token was ambiguous. In that case, the Cask::Caskroom.cask method would default to the first cask which was not always correct.

Now that we have the cask tab we can use the installed receipt to get the tap a cask came from. With both the tap and the token, we can be sure that we're loading the cask that is actually installed and not another cask from a different tap that just happens to have the same name.

TODO: Testing

[Rylan12]

@apainintheneck I just opened a PR (#17823) which duplicates some of the work here. So sorry, I didn't see this until now, otherwise I would have reviewed or modified mine to work around this.

My PR takes a slightly different approach (and covers an additional issue with named arguments), but I'm not sure it's a better solution, so this might still be the way to go with the Cask::Caskroom::casks method

[apainintheneck]

Closing in favor of #17823 which is much more thorough and comprehensive than this PR. Any necessary discussion can happen there.