Fix default table columns for Developer Portal resources

[IBeauM]

Description

Jira ticket

• registry.go: set preferred columns for all four Developer Portal types.
• jsonapi_test.go: cover column order, rendered values, and missing fields.
• BUG FIXES-20260922-113109.yaml: document the table display changes.

Example Output

Developer Portal collection tables show the resource ID followed by five preferred fields. Examples below use sample data.

Templates (tdp-templates)

ID             Name      Summary          Module Source   Module ID   Updated At
template-123   web-app   Web application  private         mod-123     2026-01-02T00:00:00Z

Applications (tdp-applications)

ID        Name      Template Name   Tfc Workspace ID   Project   Updated At
app-123   web-app   web-template    ws-123             prj-123   2026-01-02T00:00:00Z

Add-on definitions (tdp-addon-definitions)

ID               Name       Summary     Module Source   Module ID   Updated At
definition-123   database   Shared DB   private         mod-456     2026-01-02T00:00:00Z

Add-ons (tdp-addons)

ID          Name           Definition.Name   Terraform Workspace ID   Application.ID   Updated At
addon-123   app-database   postgres          ws-456                   app-123          2026-01-02T00:00:00Z

PR Checklist

• Run npx changie new or install changie to prepare a new changelog entry for the next set of release notes.
• Ensure any command changes are sensitive to these global flags:
  • --json — Force machine readable output to stdout. Does not apply to stderr.
  • --markdown — Force markdown output to stdout. Does not apply to stderr.
  • --dry-run — Don't make any actual writes or other mutations. Describe what would have changed to stderr.
  • --quiet — Only render essential content.
• [NA] Get the logging interface from the context and add debug logging for interesting conditions and nonfatal situations.
• [NA] Run make gen/screenshot if the root command output changes.
• [NA] Add the Autocomplete field to positional arguments and flags to assist shell autocomplete.

PCI review checklist

• I have documented a clear reason for, and description of, the change I am making.

• [NA] If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.

• [NA] If applicable, I've documented the impact of any changes to security controls.

  Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

[hashicorp-cla-app]

All committers have signed the CLA.

[hashicorp-cla-app]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

_{Have you signed the CLA already but the status is still pending? Recheck it.}

[brandonc]

Looks great! Just one minor changelog suggestion. Might be easiest to rm the changelog file and start over with changie new

[brandonc]

Can you change the kind to ENHANCEMENTS and reword "Improve table rendering for developer portal resources"
?

[IBeauM]

Done! Thanks