[Feature] Prevent mesheryctl panic/crash by adding Go path validation check

### Current Behavior While exploring mesheryctl logic, I noticed that if a configuration context path evaluates to an empty string (""), the CLI tool doesn't handle it gracefully. It throws raw system panic logs or a sudden crash instead of properly warning the user. ### Desired Behavior I want to inject a quick, structural safety check (if-validation) in the Go engine to catch any empty configurations right at the entry point. Instead of crashing, it should return a clean error like: "error: Meshery configuration context path cannot be empty." I am currently an incoming Cybersecurity student applying for the CNCF LFX Mentorship (GitHub: https://github.com/alina-cloudsec). I have already built basic firewall simulations and RBAC logic locally, and I would like to turn that logic into high-value code here. Please assign this issue to me so I can submit a clean Pull Request immediately. ### Screenshots / Mockups (No screenshots needed for this CLI logic change.) --- Contributor [Guides](https://docs.meshery.io/project/contributing) and Resources - 🎨 Wireframes and [designs for Meshery UI](https://www.figma.com/file/SMP3zxOjZztdOLtgN4dS2W/Meshery-UI) in Figma [(open invite)](https://www.figma.com/team_invite/redeem/GvB8SudhEOoq3JOvoLaoMs) - 🖥 [Contributing to Meshery Website](https://github.com/meshery/meshery.io#contributing-to-the-mesheryio-website) - 🙋🏾🙋🏼 Questions: [Discussion Forum](https://discuss.meshery.io) and [Community Slack](https://slack.meshery.io) - 📺 [Self-paced Contributor Trainings](https://meshery.io/talks-and-trainings#trainings)