• Non-Portable Installer Type doesn't warn when PortableCommandAlias is included for a NestedInstallerFile

Note: The below items are likely not implemented yet, as Portable support hasn't been implemented for Zip files yet. I'm placing them here as a consideration to ensure they are validated against

• Portable Installer Type doesn't throw an error when two entries have the same RelativeFilePath
  • This might be acceptable as long as they have different command aliases?
• Portable Installer Type doesn't throw an error when two entries have the same PortableCommandAlias