feat: Add tooling configs and versioning for Python and Go standards

[munlicode]

📝 Description

Currently, we are heavily focused on the TypeScript and Node.js ecosystems and do not have active Python or Go applications consuming our central tooling standards.

The initial configurations for python-standards (ruff.toml) and go-standards (.golangci.yml) were removed from the tooling monorepo to reduce overhead and visual noise (YAGNI).

When we introduce Python or Go services to the tech stack, we need to reinstate these standard configurations.

✅ Acceptance Criteria (To-do)

• Re-add the packages/python-standards directory with our ruff.toml
• Re-add the packages/go-standards directory with our .golangci.yml
• Configure Release Please to track these folders as simple component types so they generate independent versions and tags.
• Determine the distribution method (e.g., download scripts curl -o or Git Submodules) so consuming repositories can pin to specific release tags.

🔗 Context

Currently put on ice to keep the tooling repository lean and focused solely on active TypeScript/JavaScript packages (eslint, prettier, stylelint).