…pkg:path`

What was the issue?

What was meant to be a check on the parentPkg to avoid recursive
definitions wasn't actually checking the parent package, but the package
of the field itself.

It was a bug that got introduced in goadesign#3022 and never worked as expected.

Solution:

Injecting the parent package for the initial definition seems to address
this.

during marshaling/unmarshaling

…esign#3086)

* Upgrade to Go 1.18

* Use Go 1.18 in CI

* sudo does not exist on Windows

The prior code didn't always take into consideration
the case where a type has a required validation that
does not apply (e.g. object with only primitive types
that are not pointers).

This refactor moves the logic to a common method
that handles all corner cases.

…pkg:path`

What was the issue?

What was meant to be a check on the parentPkg to avoid recursive
definitions wasn't actually checking the parent package, but the package
of the field itself.

It was a bug that got introduced in goadesign#3022 and never worked as expected.

Solution:

Injecting the parent package for the initial definition seems to address
this.

When using "struct:pkg:path"

…z/goa into fix-struct-pkg-path