switched Zoom recipe to use CFBundleVersion

[mpanighetti]

• changed GROUP_TEMPLATE to CFBundleSmartGroupTemplate.xml (Zoom application no longer reports version string in a format compatible with AutoPkg)
• added extension attribute using CFBundleVersionExtensionAttribute.xml
• removed JSS_INVENTORY_NAME definition (no longer required with extension attribute addition)
• changed NAME to zoom.us to match the application bundle name (so it's compatible with the EA template; alternative would be to make a separate template file just for Zoom to accommodate the app name/product name disparity, but this felt cleaner)
• increased MinimumVersion to 1.1 (to match parent recipe)
• added space to computer group name in CFBundleVersionExtensionAttribute.xml for improved legibility

[homebysix]

Does changing the name of the extension attribute break smart groups/searches people have created using the existing EA? If so, we may want to specifically call that out for people.

[mpanighetti]

That change will create new extension attributes with the updated naming syntax the next time associated recipes run; existing searches and smart groups would continue to reference the old EAs until they are updated to point at the new EAs. It wouldn’t break those queries, but they’d no longer be pointed at currently-updated/maintained criteria. Agreed that it’s worth mentioning in documentation.