feat: Migrate Packer documentation to unified-docs system

Successfully integrated Packer website content into the web-unified-docs platform with full functionality.

## What's Working
- **Docker Setup**: Both unified-docs-api and dev-portal containers running successfully
- **Content Migration**: All Packer docs, examples, data, and assets properly migrated
- **Web Interface**: Packer documentation accessible at http://localhost:3000/packer
- **API Integration**: Redirects API working correctly (/api/content/packer/redirects)
- **Product Support**: Packer listed as supported product in unified-docs system

## Key Issues Resolved
- **Unversioned Documentation**: Configured `versionedDocs: false` for Packer in productConfig.mjs (unlike other products that use versioned structures)
- **Content Structure**: Fixed nested directory issues (docs/docs) to match expected unified-docs format
- **Redirects Format**: Converted Packer redirects from JS format to JSONC format required by unified-docs
- **Port Conflicts**: Resolved Docker port binding conflicts during development
- **Directory Structure**: Ensured proper content/packer/docs/ hierarchy vs versioned content/product/vX.X.X/ pattern

## Migration Summary
Packer now fully integrated into unified-docs with proper unversioned documentation structure. The system handles Packer's non-versioned content correctly while maintaining compatibility with other versioned products in the platform.

Author: Younique98

content/packer/.github/CONTRIBUTING.md

@@ -0,0 +1,50 @@
+---
+name: Bug Report
+about: You're experiencing an issue with Packer that is different from the documented behavior.
+labels: bug
+---
+
+<!--- Please keep this note for the community --->
+
+#### Community Note
+
+* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
+* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
+* If you are interested in working on this issue or have submitted a pull request, please leave a comment
+
+<!--- Thank you for keeping this note for the community --->
+
+When filing a bug, please include the following headings if possible. Any
+example text in this template can be deleted.
+
+#### Overview of the Issue
+
+A paragraph or two about the issue you're experiencing.
+
+#### Reproduction Steps
+
+Steps to reproduce this issue
+
+### Packer version
+
+From `packer version`
+
+### Simplified Packer Template
+
+If the file is longer than a few dozen lines, please include the URL to the
+[gist](https://gist.github.com/) of the log or use the [Github detailed
+format](https://gist.github.com/ericclemmons/b146fe5da72ca1f706b2ef72a20ac39d)
+instead of posting it directly in the issue.
+
+### Operating system and Environment details
+
+OS, Architecture, and any other information you can provide about the
+environment.
+
+### Log Fragments and crash.log files
+
+Include appropriate log fragments. If the log is longer than a few dozen lines,
+please include the URL to the [gist](https://gist.github.com/) of the log or
+use the [Github detailed format](https://gist.github.com/ericclemmons/b146fe5da72ca1f706b2ef72a20ac39d) instead of posting it directly in the issue.
+
+Set the env var `PACKER_LOG=1` for maximum log detail.

content/packer/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,8 @@
+# Copyright (c) HashiCorp, Inc.
+# SPDX-License-Identifier: BUSL-1.1
+
+blank_issues_enabled: false
+contact_links:
+  - name: Packer Community Support
+    url: https://discuss.hashicorp.com/c/packer/23
+    about: If you have a question, or are looking for advice, please post on our Discuss forum! The community loves to chime in to help. Happy Coding!

content/packer/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,35 @@
+---
+name: Feature Request
+about: If you have something you think Packer could improve or add support for.
+labels: enhancement
+---
+
+<!--- Please keep this note for the community --->
+
+#### Community Note
+
+* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
+* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
+* If you are interested in working on this issue or have submitted a pull request, please leave a comment
+
+<!--- Thank you for keeping this note for the community --->
+
+Please search the existing issues for relevant feature requests, and use the
+reaction feature
+(https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)
+to add upvotes to pre-existing requests.
+
+#### Description
+
+A written overview of the feature.
+
+#### Use Case(s)
+
+Any relevant use-cases that you see.
+
+#### Potential configuration
+
+```
+```
+
+#### Potential References

content/packer/.github/ISSUE_TEMPLATE/feature_requests.md

@@ -0,0 +1,21 @@
+---
+name: Plugin Integration Request
+about: Open request to add your plugin as a Packer integration (https://developer.hashicorp.com/packer/integrations)
+labels: integration-request
+---
+
+#### Description
+
+A written description of your plugin along with a link to the plugin repository. 
+
+#### Integration Tier
+<!--- By default all integrations are registered as community integrations.
+HashiCorp Technology partners https://www.hashicorp.com/partners/find-a-partner will be registered as a partner once verified. --->
+
+#### Checklist
+- [ ] Has valid [`metadata.hcl`](https://github.com/hashicorp/integration-template) file in plugin repository.
+- [ ] Has added integration scripts [packer-plugin-scaffolding](https://github.com/hashicorp/packer-plugin-scoffolding) to plugin repository.
+- [ ] Has added top-level integration README.md file to plugin `docs` directory.
+- [ ] All plugins components have one README.md describing their usage.
+- [ ] Has a fully synced `.web-docs` directory ready for publishing to the integrations portal.
+

content/packer/.github/ISSUE_TEMPLATE/plugin_integration.md

@@ -0,0 +1,15 @@
+---
+name: Question
+about: If you have a question, please check out our other community resources instead of opening an issue.
+labels: question
+---
+
+Issues on GitHub are intended to be related to bugs or feature requests, so we
+recommend using our other community resources instead of asking here if you
+have a question.
+
+- Packer Guides: https://www.packer.io/guides
+- Discussion List: https://groups.google.com/group/packer-tool
+- Any other questions can be sent to the packer section of the HashiCorp
+  forum: https://discuss.hashicorp.com/c/packer
+- Packer community links: https://www.packer.io/community

content/packer/.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,23 @@
+---
+name: SSH or WinRM times out
+about: I have a waiting SSH or WinRM error.
+labels: communicator-question
+---
+
+Got one of the following errors ? See if the related guides can help.
+
+- `Waiting for WinRM to become available` ?
+
+  - See our basic WinRm Packer guide: https://www.packer.io/guides/automatic-operating-system-installs/autounattend_windows
+
+- `Waiting for SSH to become available` ?
+
+  - See our basic SSH Packer guide: https://www.packer.io/guides/automatic-operating-system-installs/preseed_ubuntu
+
+Issues on GitHub are intended to be related to bugs or feature requests, so we recommend using our other community resources instead of asking here if you have a question.
+
+- Packer Guides: https://www.packer.io/guides
+- Discussion List: https://groups.google.com/group/packer-tool
+- Any other questions can be sent to the packer section of the HashiCorp
+  forum: https://discuss.hashicorp.com/c/packer
+- Packer community links: https://www.packer.io/community

content/packer/.github/ISSUE_TEMPLATE/ssh_or_winrm_times_out.md

@@ -0,0 +1,31 @@
+**DELETE THIS PART BEFORE SUBMITTING**
+
+In order to have a good experience with our community, we recommend that you
+read the contributing guidelines for making a PR, and understand the lifecycle
+of a Packer Plugin PR:
+- https://github.com/hashicorp/$REPO_NAME/blob/main/.github/CONTRIBUTING.md#opening-an-pull-request
+
+Please include tests. Check out these examples:
+
+- https://github.com/hashicorp/packer/blob/master/builder/parallels/common/ssh_config_test.go#L34
+- https://github.com/hashicorp/packer/blob/master/post-processor/compress/post-processor_test.go#L153-L182
+
+----
+
+### Description
+What code changed, and why?
+
+### Resolved Issues
+If your PR resolves any open issue(s), please indicate them like this so they 
+will be closed when your PR is merged:
+Closes #xxx
+Closes #xxx
+
+<!-- heimdall_github_prtemplate:grc-pci_dss-2024-01-05 -->
+### Rollback Plan
+If a change needs to be reverted, we will roll out an update to the code within 
+7 days.
+
+### Changes to Security Controls
+Are there any changes to security controls (access controls, encryption, logging) 
+in this pull request? If so, explain.

content/packer/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,9 @@
+version: 2
+updates:
+- package-ecosystem: gomod
+  directory: /
+  schedule:
+    interval: daily
+  allow:
+    - dependency-name: "github.com/hashicorp/packer-plugin-sdk"
+    - dependency-name: "github.com/hashicorp/hcp-sdk-go"

content/packer/.github/dependabot.yml

@@ -0,0 +1,8 @@
+# Copyright (c) HashiCorp, Inc.
+# SPDX-License-Identifier: BUSL-1.1
+
+bug:
+  - 'panic:'
+crash:
+  - 'panic:'
+