feat!: add custom names of init package in tar ball

[a1994sc]

Description

When the Zarf init package is not empty or when named init, this PR will now include that name in the pulled down tar ball.

Related Issue

Fixes #4095

Checklist before merging

• Test, docs, adr added or updated as needed
• Contributor Guide Steps followed

[netlify]

✅ Deploy Preview for zarf-docs canceled.

Name	Link
🔨 Latest commit	b0c17c6
🔍 Latest deploy log	https://app.netlify.com/projects/zarf-docs/deploys/68c6eb620146a80008b42c06

[AustinAbro321]

Hmm I don't love special casing the default init package, but I do agree that currently it's not good behavior that name changing the init package doesn't affect the package name. Another option could be removing the specialness from the init package in general and naming it zarf-package-init like every other package. This is a bigger breaking change since no doubt many users have shell scripts that pick up the init package. I think the initial naming convention was designed without custom init packages in mind.

What do the other @zarf-dev/maintainers think?