Acquia DAM RC1 release conflict

Looks good

It was intentional to require Acquia DAM for all versions of Media Acquia DAM going forward. However, we do need to add an update hook, and now that 1.1 is released, we can require that version (1.1.1 actually)

Is there a failure occurring for existing installs due to the hard dependency? The migration tool already fails gracefully and shows users an error if acquia_dam isn't installed.

We should set a soft dependency, allowing users to uninstall media_acquiadam after successfully migrating assets.

Keeping acquia_dam in the info.yml prevents users from performing the uninstall action.

Also user needs to upgrade on latest version of media_acquiadam so by default they won't get acquia_dam module enabled and However, the migration process requires the acquia_dam module, which users can enable manually through the extend menu.

Yah, so what needs to occur here is requiring Acquia Dam 1.1 and adding an update hook. We want all customers using media_acquiadam to automatically be also using Acquia Dam, hence the requirement during install (and why we need an update hook as well)

So I've updated the MR ~~ now it consists changes in composer.json file and hook_update_N (to install acquia_dam).

Looks good! Committed.