Restructure files in kbn_vislib_vis_types folder

[sulemanof]

Summary

This changes intend more comfortable usage of common options params and consistency with other places.

After further EUIfication we'll get rid of controls and editors folders

Instead of importing components from different files, now they are available just from one place:

--before

import { SwitchOption } from '../../controls/switch';
import { TextInputOption } from '../../controls/text_input';

--now

import { SwitchOption, TextInputOption } from '../../common';

--from external plugins

import {
  NumberInputOption,
  SelectOption,
  SwitchOption,
} from '../../../kbn_vislib_vis_types/public/components';

This also removes unused point-series-options directive with its template.

Checklist

Use strikethroughs to remove checklist items you don't feel are applicable to this PR.

• This was checked for cross-browser compatibility, including a check against IE11
• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• This was checked for keyboard-only and screenreader accessibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately
• This includes a feature addition or change that requires a release note and was labeled appropriately

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[flash1293]

Is there a reason why we are not keeping the folders in the hierarchy to separate general purpose components and whole editors but re-export them on the top level? Then you can import easily from the same path but you don't lose a clean folder structure below.

[sulemanof]

Is there a reason why we are not keeping the folders in the hierarchy to separate general purpose components and whole editors but re-export them on the top level? Then you can import easily from the same path but you don't lose a clean folder structure below.

Hey @flash1293 , I didn't really get your point..
Could you please attach an example of your vision?

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[flash1293]

@sulemanof Looked at the folder structure again and it's already separated as I would have done it - I misread the diff, sorry for that. LGTM

[maryia-lapata]

retest

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[maryia-lapata]

LGTM!

[elasticmachine]

Pinging @elastic/kibana-app

[dmlemeshko]

@kobelb Maybe you can help with any ideas why security tests under x-pack are failing for this PR?

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[sulemanof]

Hey @kobelb !
I fixed CI by the last commit, but it still seems weird for us. Could you please take a look ?