Refactor toolkit/tools/internal -> toolkit/tools/pkg

[mfrw]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

What does the PR accomplish, why was it needed?

This PR is broken down in 3 logical commits:

• Move all the packages form the internal directory -> pkg directory
• Update all imports for go files
• Update tools.mk to reflect the above change

git mv toolkit/tools/internal/* toolkit/tools/pkg/
fd | sad 'toolkit/tools/internal' 'toolkit/tools/pkg' --commit
# Manual edit of toolkit/scripts/tools.mk to rename `go_internal_files` -> `go_pkg_files`

Reference:

• fd: https://github.com/sharkdp/fd
• sad: https://github.com/ms-jpq/sad

Change Log

• toolkit: mv internal/* -> pkg/*
• toolkit: pkg: update imports
• toolkit: tools.mk: update post refactor of internal -> pkg/

Does this affect the toolchain?

NO

Associated issues

• toolkit: refactor all binary packages as library packages to enable building on top of the toolkit #2982
• [RFC] tools: refactor all binary packages as library packages #2983

Links to CVEs

• NA

Test Methodology

• Local Build

• Full Build: link

[dmcilvaney]

I'm open to this, although maybe we want to do this right after we snap for 3.0 just for a clean break?