devel/rubygem-sucker_punch: Update to 3.2.0

Changes:	https://github.com/brandonhilkert/sucker_punch/blob/master/CHANGES.md

Mk/**ruby.mk: Switch from USE_RUBY=yes to USES=ruby

Switch from Mk/bsd.ruby.mk to Mk/Uses/ruby.mk

Notable changes are.

- Mk/bsd.ruby.mk is moved to Mk/Uses/ruby.mk.
- USE_RUBY=yes is replaced with USES=ruby.
- USE_RUBY_EXTCONF is replaced with USES=ruby:extconf.
- USE_RUBY_RDOC is replaced with USES=ruby:rdoc.
- USE_RUBY_SETUP is replaces with USES=ruby:setup.
- RUBY_NO_BUILD_DEPENDS and RUBY_NO_RUN_DEPENDS are replaced with
  USES=ruby:{build,none,run}.
- RUBY_REQUIRE isn't used anywhere, so removed.
- USES=gem now implies USES=ruby.

This is mainly the work of yasu@ at https://reviews.freebsd.org/D27863

I have just made some cosmetic changes and ran exp-run to test that the
tree is not in a BROKEN state.

Approved by:	portmgr
Differential Revision:	https://reviews.freebsd.org/D37925

Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)

Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.

devel/rubygem-sucker_punch: Update to 3.1.0

Changes:	https://github.com/brandonhilkert/sucker_punch/blob/master/CHANGES.md

devel: remove 'Created by' lines

A big Thank You to the original contributors of these ports:

  *  "Waitman Gobble" <uzimac@da3m0n8t3r.com>
  *  <jkoshy@FreeBSD.org>
  *  Aaron Dalton <aaron@FreeBSD.org>
  *  Aaron Dalton <aaron@daltons.ca>
  *  Aaron H. K. Diep <ahkdiep@gmail.com>
  *  Aaron Hurt <ahurt@anbcs.com>
  *  Abel Chow <abel_chow@yahoo.com>
  *  Adam McLaurin
  *  Adam Saponara <as@php.net>
  *  Adam Weinberger <adamw@FreeBSD.org>
  *  Ade Lovett <ade@FreeBSD.org>

devel/rubygem-sucker_punch: Add rubygem-sucker_punch 3.0.1

Sucker Punch is a single-process Ruby asynchronous processing library. This
reduces costs of hosting on a service like Heroku along with the memory
footprint of having to maintain additional jobs if hosting on a dedicated
server. All queues can run within a single application (eg. Rails, Sinatra,
etc.) process.

Sucker Punch is perfect for asynchronous processes like emailing, data
crunching, or social platform manipulation. No reason to hold up a user when you
can do these things in the background within the same process as your web
application.

Sucker Punch is built on top of concurrent-ruby. Each job is setup as a pool,
which equates to its own queue with individual workers working against the jobs.
Unlike most other background processing libraries, Sucker Punch's jobs are
stored in memory. The benefit to this is there is no additional infrastructure
requirement (ie. database, redis, etc.). However, if the web processes are
restarted with jobs remaining in the queue, they will be lost. For this reason,
Sucker Punch is generally recommended for jobs that are fast and non-mission
critical (ie. logs, emails, etc.).

WWW: https://github.com/brandonhilkert/sucker_punch