Make rule vue/no-unregistered-components ignore recursive components

[arrudaje]

Right now when we use recursive components (when we want to use the current component inside of itself - with the example of a Note component that can have a number of replies, that look and behave exactly like the Note component, and they stack inside of one another), eslint-plugin-vue complains against it, making us disable this rule every time we want to use a recursive component.

The suggestion is to include a new argument to the rule, ignoreRecursive, which, if true, checks whether the name of the parent component is the same as the child component (making it thus a recursive component), not warning about this rule on it.

Resolves #1304

[ota-meshi]

Thank you for this PR and report! Sorry for the late reply.

I didn't know that I could use self component in <template> using the same name as name option.
I think it's a bug, so I don't think it's necessary to add option.

[arrudaje]

Thank you for this PR and report! Sorry for the late reply.

I didn't know that I could use self component in <template> using the same name as name option.
I think it's a bug, so I don't think it's necessary to add option.

@ota-meshi Thank you for your reply!
Actually it's a feature in Vue. I don't know why they decided to remove the guide (v2) for recursive components in v3, but I found a mention in this page https://v3.vuejs.org/api/options-misc.html#name.
Also, it's very useful when you want to render a tree-like component, such as a comment thread (with many replies one inside the other) or an expandable menu.
Please tell me what you think, and this probably can clear out some of the comments you made here also, although I will try to work on them.

[ota-meshi]

LGTM! Thank you!