[REQ] [CORE] Prevent Stack Overflows when cycles present in spec

[spacether]

Is your feature request related to a problem? Please describe.

Per a discussion in: #4906
It is possible to create stack overflows with some of the below cases:

• a oneof model which alloF includes the composed schema that includes it
  There are probably other cases here.
• what about a grandparent, a parent which allof inherrits the grandparent, a child which allof inherrits the parent AND allof inherrits the grandparent

Our code should detect these cycles and stop, warning the user to fix their spec rather than hitting the stack overflow.
Currently we hit a stack overflow.

Describe the solution you'd like

Perhaps error out and warn the user?
Or allow the cycle but stop moving through it after we detect the cycle?

[dtam-atl]

Hey! I have a question related to this as I'm bumping into this bug right now. Is a cycle uncompliant with the spec? It doesn't seem to be mentioned anywhere in the spec what's meant to happen in that case.

[spacether]

Hey! I have a question related to this as I'm bumping into this bug right now. Is a cycle uncompliant with the spec? It doesn't seem to be mentioned anywhere in the spec what's meant to happen in that case.

Cycles are allowed and compliant with the spec as far as I know. As you said it is not mentioned there.