fix: Parsing of west.yml when determening NCS version

[TjazVracko]

Description

Turns our a "project" within west.yml does not need to contain the repo-path key.
I fix this by using .get instead of [].

Areas of interest for the reviewer

All

Checklist

• My code follows the style guidelines as defined by IRNAS.
• I have performed a self-review of my code.
• My changes generate no new warnings.
• I added/updated source code documentation for all newly added or changed
  functions.
• I updated all customer-facing technical documentation. - This PR introduced only internal facing changes.

After-review steps

• Reviewer can merge and delete the branch.

[TjazVracko]

• fix: Parsing of west.yml when determening NCS version #114 👈
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @TjazVracko and the rest of your teammates on Graphite

[MarkoSagadin]

Thank you for finding this!

I see that I actually implemented this function wrongly initially, the .get() accessor is the correct way to do it, not with with the try, except blocks.

But this means that with .get() the try, except blocks are redundant. Can you remove them?

Additionally, in the same light, is the "revision" field also optional?
If yes, could you also add a check for that?

[TjazVracko]

Thank you for finding this!

I see that I actually implemented this function wrongly initially, the .get() accessor is the correct way to do it, not with with the try, except blocks.

But this means that with .get() the try, except blocks are redundant. Can you remove them?

Additionally, in the same light, is the "revision" field also optional?
If yes, could you also add a check for that?

This section of the docs describes what is mandatory and what is optional: https://docs.zephyrproject.org/latest/develop/west/manifest.html#id7
The revision is optional...
I will add this logic as well.

[MarkoSagadin]

Thank you!