Updates embargo scripts.

[scherztc]

Fixes #1165

The embargo scripts are not being used in cron since the date -v function is crashing. We need to clean up these scripts and then set them in crontab.

We have also separated the notification and releasing into their own scripts instead of doing it crontab.

[hortongn]

@scherztc Hard coding RAILS_ENV=production means these scripts won't work in development. Is that ok? Thoughts?

[scherztc]

Yeah. I had concerns.
I didn't see environment in the .env files.
So, I am working to find a way to pull that information from the environment.
Any ideas?

[hortongn]

Perhaps the same way we handle script/restart_sidekiq.sh. We call that script with a parameter to specify the right environment. Like script/restart_sidekiq.sh development or script/restart_sidekiq.sh production

Look at the script/restart_sidekiq.sh source for how we're using ENVIRONMENT to grab and use the parameter.

[hortongn]

@scherztc You can remove the THREADS=$2 and RVM=$3 since we're not using those variables. Also remove the banner lines. We want cron tasks to run without output unless there's an error. Cron sends emails whenever there's output from a cron job.

[scherztc]

I tested this on DEV and it worked successfully with the application in INLINE mode verse SIDEKIQ mode.
I repeat these scripts works on DEV