@Eric.C.Miller and @rocketwiz have provided some great answers, I'll probably only offer up some minor details (in a lengthy reply) and perhaps a different way of explaining some of the same concepts.
As @Eric.C.Miller mentioned, Hub Mesh is networking across Hubitat Hub's. The best way I can think to explain it is through examples. If you have 1 HE hub with Zigbee and other devices paired / configured, these typically produce events, like a motion sensor detecting motion or detecting no motion, a contact sensor opening or closing, a light turning on and off, etc. You would then typically setup automations triggered by some of these events and call commands on devices in response, e.g. when a motion sensor activates, turn the light on. In these examples, these three sets of devices may all be paired to HE hub 1, forming part of it's Zigbee mesh, but they can also be shared via Hub Mesh with a HE hub 2. All the events that are produced on hub 1 are automatically replicated on hub 2, meaning that anything you choose to setup on hub 2, like another automation, can work with the replicated version of the device as though it was paired with hub 2. Similarly if you call a command in an automation on hub 1 that acts on devices shared with hub 2, the same events that result from that command will also be represented on hub 2, e.g. turning the light on. The replication of events and other details sync in both directions as well, you can have automations on either hub to suit whatever it is you need.
So, to answer your question about the dongles...
Unless you have a need to be able to see events they produce on the (potential) hub in the shop, and you won't have any need to issue commands on them from the shop hub, then there would be no need to share them via Hub Mesh.
All that said, I make this out to be a much bigger thing than it really is, it literally takes < 1 minute to open up the Hub Mesh settings page and share a device across HE hubs, so there's no upfront decision you have to make now about whether to use it.
I think the term "mostly hands off" is accurate. There can be teething problems, sometimes in the beginning, sometimes when things change, like removing a device, etc. But for the most part, once you work through and resolve an issue, which on the whole are rare, then you should be fine.
There is a guide in the Documentation for setting up a strong mesh network,
https://docs2.hubitat.com/how-to/build-a-solid-zigbee-mesh
largely focusing on @rocketwiz 's recommendation of fanning out with repeaters and then end-devices from the HE hub in the centre. There are other considerations like potential for clashes with other 2.4GHz networks and the importance of selecting an appropriate channel and power settings. Certain device types and / or versions of the Zigbee protocol used can also be a factor, so it is worth confirming the support for a device ideally before making a purchase, typically looking up officially supported devices or posting a question on the Community in case there is a custom driver, and to gauge other peoples experiences.
My gut feel as well is to incorporate a second hub for the shop. But depending on your need to get it up and running, you could try by starting out with one, either in the shop or in the house, see what works with that setup, then adapt it as you need to, potentially purchasing the second hub after you have trialed one. It would also give you a chance to assess the platform in more detail.
In terms of alternatives for extending your ability to pair Zigbee devices in the shop, if they can't reach the house, you can look at other platforms like Z2M on a raspberry pi, or something similar, but if it is purely Zigbee connectivity, another HE hub would be far easier to work with if that is all you need it for. I would only bring in another platform if it is going to give you additional functionality beyond what HE can deliver, which would not be the case necessarily for Zigbee devices.