chore(Rest): Suggestion to Rest work

[lordrip]

Context

This PR adds a few suggestions to the existing KaotoIO#1524 PR.

It also fixes the problem of some typings not loading.

relates to: KaotoIO#1490

[lordrip]

I thought this wasn't needed, so I removed it from the dependency list

[lordrip]

I added this type that resembles the official OpenApi 3.0 schema

[lordrip]

This is the list of methods that Rest supports

[lordrip]

While this worked, the OpenApi spec defines other fields that we might be iterating over if present:

export interface OpenApiPath {
    /**
     * Allows for an external definition of this path item. The referenced structure MUST be in the format of a Path Item Object.
     * If there are conflicts between the referenced definition and this Path Item's definition, the behavior is undefined.
     */
    $ref?: string;
    /** An optional, string summary, intended to apply to all operations in this path. */
    summary?: string;
    /** An optional, string description, intended to apply to all operations in this path. CommonMark syntax MAY be used for rich text representation. */
    description?: string;
    /** A definition of a GET operation on this path. */
    get?: OpenApiOperation;
    /** A definition of a PUT operation on this path. */
    put?: OpenApiOperation;
    /** A definition of a POST operation on this path. */
    post?: OpenApiOperation;
    /** A definition of a DELETE operation on this path. */
    delete?: OpenApiOperation;
    /** A definition of a OPTIONS operation on this path. */
    options?: OpenApiOperation;
    /** A definition of a HEAD operation on this path. */
    head?: OpenApiOperation;
    /** A definition of a PATCH operation on this path. */
    patch?: OpenApiOperation;
    /** A definition of a TRACE operation on this path. */
    trace?: OpenApiOperation;
    /** An alternative server array to service all operations in this path. */
    servers?: OpenApiServer[];
   ...
}

So better to iterate only on the intended methods, hence the need for the valid methods array above.

[lordrip]

The constructor of the CamelRestVisualEntity class is:

constructor(public restDef: { rest: Rest }) {

but we were passing rest: Rest directly

[lordrip]

Here we're removing these properties from the form, since it would be better to configure them through the UI, like adding nodes and stuff.

[lordrip]

I renamed this rest to restDef so it's easier to reason about what is being edited.

[lordrip]

This was preventing the configuration form from loading because we were assigning the restDef instead of the rest property.

[lordrip]

Since we are not providing the appropriate get, post, etc... nodes, would it be better to don't show this interaction?

[lordrip]

getRootUri should return either string or undefined, here we were returning Rest