Forward slash in environment name causes Postman import failure

[igor-topolski]

I have checked the following:

• I use the newest version of bruno.
• I've searched existing issues and found nothing related to my issue.

Describe the bug

Issue #219 already describes a scenario for collections, but I did not find one for environments.

If the environment name contains /, the import fails with a non-descriptive error.

Here's an example payload causing a silent failure

{
	"id": "099ecab4-b9ee-4290-b33a-50357f4eae0a",
	"name": "Some / Environment / Name",
	"values": [
		{
			"key": "my-key",
			"value": "",
			"enabled": true
		}
	],
	"_postman_variable_scope": "environment",
	"_postman_exported_at": "2024-04-29T00:00:00.000Z",
	"_postman_exported_using": "Postman/10.24.24"
}

I believe it either should allow / in collection names or the error should provide clear guidelines on validation error.

.bru file to reproduce the bug

No response

Screenshots/Live demo link