fix(types): fix collision between js/core and plugins

[shortcuts]

Summary

There was a collision between the AutocompleteOptions/AutocompletePlugin types in js/core, which is now partially solved by making them looser.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit a6cde30:

Sandbox	Source
@algolia/autocomplete-example-github-repositories-custom-plugin	Configuration
@algolia/autocomplete-example-multiple-datasets-with-headers	Configuration
@algolia/autocomplete-example-playground	Configuration
@algolia/autocomplete-example-query-suggestion-with-categories	Configuration
@algolia/autocomplete-example-query-suggestions-with-hits	Configuration
@algolia/autocomplete-example-query-suggestions-with-inline-categories	Configuration
@algolia/autocomplete-example-query-suggestions-with-recent-searches-and-categories	Configuration
@algolia/autocomplete-example-query-suggestions-with-recent-searches	Configuration
@algolia/autocomplete-example-query-suggestions	Configuration
@algolia/autocomplete-example-react-renderer	Configuration

[shortcuts]

@francoischalifour I've removed the TState implementation from the PR and will handle it in a separate one.

[francoischalifour]

Nice! Good to merge once the last piece of feedback is addressed.

[francoischalifour]

Why do we need this?

[shortcuts]

On my side, running the actual yarn build in parcel 2.0.0-beta.2 will output the build in the root folder.

Could you confirm this is also the case for you? If so, I'll update the other examples

[francoischalifour]

It builds it in the right folder for me.

What command did you run and from where?

[shortcuts]

From the example folder (the root), with yarn build, yarn start works though.

[francoischalifour]

Indeed!