Add "📦 Warehouse" team to Fleet's best practice teams

[Sampfluger88]

• Added "📦 Warehouse" team to Fleet's best practice teams
• Fixed "📦 Warehouse" team links on the Digital Experience page
• Fixed link in warehouse request template https://github.com/fleetdm/confidential/pull/10186

[allenhouchins]

Hey @Sampfluger88 just a couple of thoughts/comments...

• I will need to add a Warehouse team to dogfood via GitOps so its persistent and will also need to consider what settings we want these devices to have applied, if any.
• I am hesitant to call this a best practice for customers to follow. Most customers don't have this issue because they don't treat their device management platform as their asset management system. The ones that do, typically keep these devices assigned to an "IT Inventory" user but keep the device in the right team so the device always has the appropriate settings applied or auto-applied once it comes back online. Once the device is handed or mailed out to a user, IT assigns the device to the user on the host record. Something we will be able to do in the coming weeks.
• If we do stick with this Warehouse team workflow, then we'll also want to enhance any of our own internal process documentation to instruct the user to transfer the device to the more appropriate team once they receive it otherwise these devices are going to be without a lot of settings, apps, etc. which could lead to a poor employee experience.

CC: @noahtalerman for awareness, thoughts, discussion at next dogfood meeting?

[noahtalerman]

Created a dogfood issue here so we don't forget to hit this at the next dogfooding sync.

[Sampfluger88]

@allenhouchins All that makes sense to me. The guide change was simply me best attempt at handbook-first as it's the only place I found our existing teams documented. Happy to go with the "IT inventory" approach. Whatever best reflects our customers' config.

[Sampfluger88]

Closing in favor of https://github.com/fleetdm/fleet/issues/27978