Changed examples deleting Elasticsearch indices

[mnocon]

Target: master, 4.6, 3.3

Community feedback:

Hi, can you please update https://doc.ibexa.co/en/latest/update_and_migration/from_4.5/update_from_4.5/#updateelasticsearch-schema 
to indicate that the DELETE curl with 'all' is highly destructive and should not be run on elastic.co hosted servers.
instead the curl should target the specific CMS indexes like 'default*'

I've verified locally that it works by running the Elasticsearch container and then executing:

php bin/console ibexa:reindex
curl --request DELETE 'http://0.0.0.0:9200/default_content*'
curl --request DELETE 'http://0.0.0.0:9200/default_location*'
php bin/console ibexa:elasticsearch:put-index-template
php bin/console ibexa:reindex

which is enough to solve the issue described in https://issues.ibexa.co/browse/IBX-3758, but potentially less desctuctive.

[github-actions]

Preview of modified Markdown:

• docs/search/search_engines/elasticsearch/elasticsearch_overview.md
• docs/update_and_migration/from_4.5/update_from_4.5.md

[julitafalcondusza]

Suggested change

	Use the command as in the following example:
	Use the commands as in the following example:

[vidarl]

Hmm.. I am not sure how destructive it is when running on elastic.co servers ( if it deletes metadata needed by the service too ?), but if we don't delete everything, we must document better what we delete. These default_ values comes from the template, https://doc.ibexa.co/en/latest/search/search_engines/elasticsearch/configure_elasticsearch/#define-a-template

So with out-of-the-box config, the new documentation is correct. But with changed templates, the commands needs to be adjusted accordingly

[github-actions]

Preview of modified files

Preview of modified Markdown:

• docs/search/search_engines/elasticsearch/elasticsearch_overview.md
• docs/snippets/elasticsearch_clear_index.md
• docs/update_and_migration/from_4.5/update_from_4.5.md

[vidarl]

Looks fine to me ( I haven't tested this though)
Feel free to implement my two suggestion or choose to ignore them

[vidarl]

As described in the PR description:

DELETE curl with 'all' is highly destructive and should not be run on elastic.co hosted servers.

Just a suggestion:
So, maybe write that... That if you are hosting ES yourself, and only use if for Ibexa DXP caching, you maybe just do a quick curl --request DELETE 'https://elasticsearch:9200/_all'. But if are using elastic.co hosted services or possibly have other data stored in your ES, then take the long way and check what to explicit delete

[vidarl]

Possibly show the exact curl commands for getting this?

[mnocon]

Thank you Vidar, added the suggestions in 4249e73

[mnocon]

@ibexa/documentation I've added some changes, you might want to have another look since your last review