Updating a site via the Playbook fails due to field_abstract type mismatch

[alxp]

PR: Fixes for running provision on an existing site. #210

When running the islandora-playbook on an existing site, the "import features" task now fails with the following error:

TASK [webserver-app : Import features] *****************************************
Wednesday 30 March 2022  09:42:45 -0300 (0:00:00.355)       0:04:44.982 ******* 
 fatal: [default]: FAILED! => {"changed": true, "cmd": ["/var/www/html/drupal/vendor/bin/drush", "--root", "/var/www/html/drupal/web", "-y", "fim", "islandora_core_feature,islandora_defaults"], "delta": "0:00:06.344474", "end": "2022-03-30 12:42:51.494385", "msg": "non-zero return code", "rc": 1, "start": "2022-03-30 12:42:45.149911", "stderr": "\nIn FieldStorageConfig.php line 375:\n                                                                               \n  Cannot change the field type for an existing field storage. The field stora  \n  ge node.field_abstract has the type string_long.                             \n                                                                               ", "stderr_lines": ["", "In FieldStorageConfig.php line 375:", "                                                                               ", "  Cannot change the field type for an existing field storage. The field stora  ", "  ge node.field_abstract has the type string_long.                             ", "                                                                               "], "stdout": "", "stdout_lines": []}

This is due to the issue Change abstract from string to text #1977

This raises the fact that the playbook is running an import features task that should not be necessary after the module is installed.

Since we have decided to not try and alter the schema, as discussed in recent tech calls, we should remove this step so that re-running the playbook on an existing site (a normal feature of Ansible to keep running servers updated) should not drastically alter an existing site.

That said, an update hook to change an existing site's field schema would still be helpful for users who do want to keep up with Islandora changes, but that's for a separate ticket and discussion.