Don't nest unnamed resource groups, resources and examples

[kylef]

Currently the Paw plugin keeps the API Blueprint AST structure intact when importing within the Paw hierarchy. Unfortunately this provides poor UX when there are unnamed resource groups and unnamed examples (most examples are usually unnamed).

Let's take a look at an example, here is the previous behaviour of the Polls API example blueprint:

There are various annoyances in this example:

• There is an "Unnamed" resource group, which results in an unnecessary group within Paw
• None of the examples are named so they are all called "Example"
• There is only a single example in these cases, so there is no need to create a group for the single element. In this case we can just create the request with the name of the action when there is no example name.

Here is how it looks afterwards:

Closes #8

[pksunkara]

Shouldn't this be resourceGroup?

[pksunkara]

lgtm. I might be confused on the variable names though. Maybe the request and requestGroup are names for PAW?

[kylef]

@pksunkara The object types are called Request and RequestGroup inside Paw.