removes errant console.logs from EuiTour

[dimitropoulos]

see: #2766 (comment)

I noticed over the weekend whilst exploring EuiTour that there are console.log statements that are firing when you step through. I checked with @thompsongl and it appears that these were added during development with the intention of removal prior to merge. This PR removes them.

Check against all themes for compatibility in both light and dark modes

• [ ] Checked in mobile
• [ ] Checked in IE11 and Firefox
• [ ] Props have proper autodocs
• [ ] Added documentation examples
  Added or updated jest tests
  Checked for breaking changes and labeled appropriately
• [ ] Checked for accessibility including keyboard-only and screenreader modes
  A changelog entry exists and is marked appropriately (it seemed to me that a changelog for such a thing is not necessary but I'm happy to add one if anyone feels it adds value)

[kibanamachine]

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

[chandlerprall]

Good to have you back in the repo 😺

Could you expand the PR description to include the goal? It should keep the reference to the source comment, but not having to jump to another page and digest a comment thread will help review and if someone digs through the commit log in the future it makes the change easier to understand. It'd also be nice to retain the reference checklist, even if most of it is unapplicable and crossed out.

Otherwise, this looks good to go. ❤️

[chandlerprall]

jenkins test this

[dimitropoulos]

absolutely! sorry :)

I made this PR from GitKraken and the checklist isn't visible there. I'll go grab one.

[kibanamachine]

Preview documentation changes for this PR: https://eui.elastic.co/pr_3513/