Add config-converter extension

[erfgypO]

Description

Screencast

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Congratulations on your new Raycast extension! 🚀

Due to our current reduced availability, the initial review may take up to 10-15 business days

Once the PR is approved and merged, the extension will be available on our Store.

[greptile-apps]

PR Summary

This PR adds a new Config Converter extension that converts JSON objects to shell environment variables, with options for regular and base64-encoded output.

• README.md is too minimal and needs significant expansion to include usage instructions, examples, and proper documentation of the functionality
• Consider wrapping launchCommand in try-catch blocks in both json2environment.ts and json2environmentB64.ts for better error handling
• Could simplify error handling in processJson.ts by using showFailureToast from @raycast/utils instead of manual showToast with failure style
• Add subtitle to both commands in package.json with "Config Converter" to match extension title
• Consider adding screenshots in a metadata folder since this is a new extension, showing example input/output

_{💡 (1/5) You can manually trigger the bot by mentioning @greptileai in a comment!}

_{12 file(s) reviewed, 10 comment(s)
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

style: README needs more content: description of what the extension does, installation/usage instructions, and examples of JSON to environment variable conversion. See https://developers.raycast.com/basics/prepare-an-extension-for-store#readme

[greptile-apps]

style: Consider adding a subtitle to distinguish between the two commands, e.g. 'Convert JSON to environment variables'

[greptile-apps]

style: Consider adding a subtitle to distinguish between the two commands, e.g. 'Convert JSON to base64-encoded environment variables'

[greptile-apps]

style: Consider wrapping processJson call in try/catch for better error handling

Suggested change

	export default async function main() {
	await processJson(false);
	export default async function main() {
	try {
	await processJson(false);
	} catch (error) {
	console.error(error);
	throw error;
	}

[greptile-apps]

logic: This condition will return undefined if path is not provided for primitive values. Should be if (typeof obj !== 'object') {

[greptile-apps]

style: for...in loop on objects should check hasOwnProperty to avoid prototype chain properties

Suggested change

	for (const key in obj) {
	for (const key in obj) {
	if (Object.prototype.hasOwnProperty.call(obj, key)) {

[greptile-apps]

style: Consider using a more specific type than any to better type-check JSON values, e.g. string | number | boolean | null | object | Array<unknown>