security/libgcrypt: Make static an option

Static linked binaries, due to the fact that they're statically linked,
can pose a security risk should a library be updated and depending
software not be recompiled and linked. This was a hot topic on BUGTRAQ
about 25 years ago.

The default is to build static libraries so as not to alter the package
avoiding a POLA violation.

PR: 255735
Submitted by: Daniel Engberg <daniel.engberg.lists@pyret.net> (mostly)
Reported by: Daniel Engberg <daniel.engberg.lists@pyret.net>
Reviewed by: cy
Tested by: cy
MFH: 2021Q2

(cherry picked from commit 527821a60c9f2e706a0549ac23c8ddc6d8b778c3)