Reformat Jamf extension XMLs to Jamf Pro import-ready extensionAttribute schema

[Copilot]

Description

jamf/extensions/*.xml was inconsistent: only BitLocker files were in Jamf Pro extension-attribute upload format, while the rest were raw scripts. This change normalizes extension XMLs so they can be imported directly in Jamf Extension Attributes without manual wrapping.

• Scope
  • Reformatted 13 extension files in jamf/extensions/ from script-only XML content to Jamf Pro <extensionAttribute> payloads.
• Normalization applied
  • Added/standardized: <displayName>, <description>, <dataType>string</dataType>, <scriptContentsMac>, and <scriptContentsWindows/>.
  • Preserved existing script logic and output behavior; only representation/packaging changed.
  • Encoded script bodies for XML-safe Jamf import (entity escaping + CR line delimiters), aligned to get-bitlocker-status-all-users.xml.
• Example format

  <extensionAttribute>
    <displayName>Parallels Get Edition</displayName>
    <description>Get the Edition of Parallels Desktop.</description>
    <dataType>string</dataType>
    <scriptContentsMac>#!/bin/bash&#13;
  ...
    </scriptContentsMac>
    <scriptContentsWindows/>
  </extensionAttribute>

Type of change

Please delete options that are not relevant.

• Documentation Change
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have run tests that prove my fix is effective or that my feature works