Show all crc dataset on group show page either work  in review or published

See merge request FDM/rdm-system/rdms!135

Fixed visibility for crc_member

See merge request FDM/rdm-system/rdms!134

Tombstone feature moved to workflow section

See merge request FDM/rdm-system/rdms!133

Creates rake for setup users

See merge request FDM/rdm-system/rdms!129

Set default value for role and license

See merge request FDM/rdm-system/rdms!128

Cannot save more than 11 complex records in the submission form

See merge request FDM/rdm-system/rdms!127

Create assets on first run in production mode

See merge request FDM/rdm-system/rdms!125

Currently, starting RDMS after rebuilding and reinstalling it from
scratch in `RAILS_ENV=production` mode fails because assets are not
created automatically. I'd prefer to put the required commands into the
`Dockerfile`, but this doesn't work currently because the path used to
store these assets is a Docker volume shared between multiple Docker
containers, which are not available at build time of these container
images/execution time of the corresponding `Dockerfile`. Therefore, for
the time being, we execute the commands in the container's
`hyrax/docker-entrypoint.sh`.

Merge branch '32-generate-random-passwords-with-securerandom-instead-of-devise-friendly_token' into 'develop'

Generate random passwords with SecureRandom instead of Devise.friendly_token

See merge request FDM/rdm-system/rdms!123

Remove hyrax/seed/crc_users.json

See merge request FDM/rdm-system/rdms!126

According to @anusha, `hyrax/seed/crc_users.json` isn't needed anymore,
so let's remove it.

It seems that `User` objects can't be created with a `nil` password, so we have to set a password even for Shibboleth and ORCID user accounts, even though that password is never supposed to be used. Currently, we use `Devise.friendly_token` for this, but `SecureRandom` seems a better choice since it doesn't incur external dependencies/3rd party libraries (even though we currently use `Devise` nonetheless).

Note: This does create passwords with binary/non-printable characters.
Given the 32 byte length chosen, this gives us 256 bit entropy per
password.

Replace all hard-coded admin user to correct one

See merge request FDM/rdm-system/rdms!122

add manual assets precompile documentation to readme

See merge request FDM/rdm-system/rdms!121

changes for tombstone visibility

See merge request FDM/rdm-system/rdms!119