chore: Changes to metadata files

[m-strzelczyk]

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• Make sure to open an issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• Follow the Samples Style Guide
• Ensure the tests and linter pass
• Communicate test infrastructure changes, i.e. API enablement, secrets
• Appropriate docs were updated (if necessary)

🛠️ Fixes #<issue_number_goes_here>

[conventional-commit-lint-gcf]

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot
https://conventionalcommits.org/

[grayside]

Is _desc meant to clarify that it's a string value? Are these values separately used in the tool? If not maybe they should be combined? Or perhaps requirements_desc could be moved as requirements.description?

[m-strzelczyk]

The _desc suffix is there, because right after this we have a section [requirements] and the names collide. So I quickly added the _desc suffix to requirements fields. I added the suffix to effects as well for consistency.

[grayside]

This makes sense for prototype, it might be good to move the error suppression into a separate setting, maybe a "warnOnFailure" that would allow the tool to suppress the error but still log as part of the tool's UX that something went wrong.

[m-strzelczyk]

This could work when we have only one command, but if there are multiple commands and we want to ignore error for only some of them, it gets more complicated.

Definitely something to consider if this gets to evolve to full project.