Allow user to create issues within the docs-site

[anishagg17]

At the bottom of each example in docs there should be a link which redirects user to new-issue page of this repo .

Also, current issues related to the component can be displayed beneath it using this api,

https://api.github.com/repos/elastic/eui/issues?labels=tables

label would be slug used for routing thus making is automatically fetch correct issues

[cchaos]

This is a very interesting idea and could help streamline the bug/feature requests and ensure they're named/titled properly in Github so they're easier to search for.

Though I do have some concerns and caveats.

Concerns

1. I worry that this can overcrowd the already verbose docs and some pages include more than one component so how do you distinguish?
2. How would we offer these gracefully without saying "Hey this component is buggy, here's all the known bugs". It might turn people off from using it if they see that there's currently 17 issues associated with EuiDataGrid.

Caveat

1. I kind of like the idea of a link to open an issue with the title already filled with the component name (we do a similar thing in Kibana) for the reasons stated above. However, while your example uses a label we should not go down the path of adding a Github label for every single component.

2. And again, where do we gracefully add this link? Maybe it should only exist in the new Playground area.

---

We may just need to make the link to the repo more apparent and push people to it for bug/feature requests. This could be in the primary side-nav maybe under the gear icon, or on the homepage.

[nyurik]

Could there be a edit this page link in addition to or instead of this? I find it very useful in most of Elastic and other project's documentation to direct users to the right docs file -- this way users can easily contribute minor documentation fixes without too much effort, and often use GitHub's online editor to propose the change.

P.S. #3767 created

[cee-chen]

Closing this as won't implement. We're more likely to lean towards linking users towards the source code of the components rather than opening an issue (#491).