fix: use ~/.meshery directory for temporary files instead of working

[souvikinator]

…directory

Description

This PR fixes #648

Notes for Reviewers

Addresses the issue of temporary file handling during Docker Compose to Kubernetes manifest conversion in Meshery.

Previously, temporary files were being created in the working directory (./) which caused permission issues in a containerized environment.

NOTE: using ~/.meshery instead of ./ is a hypothesis, if this fails we might want to try using os.TempDir() or os.CreateTemp()

The Problem:

• Temporary files (temp.data and result.yaml) were being created in the current working directory
• This led to permission denied errors in containerized environments where the working directory might not be writable

The Solution:

• Created a dedicated ~/.meshery directory for temporary file operations

Testing Done:

• Works fine locally

Signed commits

• Yes, I signed my commits.

[leecalcote]

@souvikinator - https://github.com/meshery/meshkit/actions/runs/12894300696/job/35952644600?pr=649

  Running [/home/runner/golangci-lint-1.63.4-linux-amd64/golangci-lint run] in [/home/runner/work/meshkit/meshkit] ...
  level=warning msg="[runner] Can't run linter goanalysis_metalinter: buildir: failed to load package reference: could not load export data: no export data for \"github.com/docker/distribution/reference\""
  level=error msg="Running error: can't run linter goanalysis_metalinter\nbuildir: failed to load package reference: could not load export data: no export data for \"github.com/docker/distribution/reference\""