Update bcrypt to a version that builds on armhf

What does this MR do?

Update bcrypt to new upstream version after verifying the build failure in armhf is fixed. Related merge request !18828 (merged)

Screenshots (strongly suggested)

(sid_armhf-dchroot)praveen@abel:~$ gem install -v 3.1.13 bcrypt
Building native extensions. This could take a while...
ERROR:  Error installing bcrypt:   
        ERROR: Failed to build gem native extension.

    current directory: /home/praveen/.gems/gems/bcrypt-3.1.13/ext/mri
/usr/bin/ruby2.7 -I /usr/lib/ruby/vendor_ruby -r ./siteconf20210308-27328-1p6ka0m.rb
 extconf.rb
creating Makefile

current directory: /home/praveen/.gems/gems/bcrypt-3.1.13/ext/mri
make DESTDIR\= clean

current directory: /home/praveen/.gems/gems/bcrypt-3.1.13/ext/mri
make DESTDIR\=
compiling bcrypt_ext.c
compiling crypt_blowfish.c
compiling crypt_gensalt.c
compiling wrapper.c
arm-linux-gnueabihf-gcc  -D__SKIP_GNU -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64   -c -o x86.o x86.S
x86.S: Assembler messages:
x86.S:202: Error: junk at end of line, first unrecognized character is `,'
make: *** [<builtin>: x86.o] Error 1

make failed, exit code 2

Gem files will remain installed in /home/praveen/.gems/gems/bcrypt-3.1.13 for inspection.
Results logged to /home/praveen/.gems/extensions/arm-linux/2.7.0/bcrypt-3.1.13/gem_make.out
(sid_armhf-dchroot)praveen@abel:~$ gem install -v 3.1.14 bcrypt
Fetching bcrypt-3.1.14.gem
Building native extensions. This could take a while...
Successfully installed bcrypt-3.1.14
Parsing documentation for bcrypt-3.1.14
Done installing documentation for bcrypt after 7 seconds
1 gem installed
(sid_armhf-dchroot)praveen@abel:~$ uname -a
Linux abel 4.19.0-14-armmp-lpae #1 SMP Debian 4.19.171-2 (2021-01-30) armv7l GNU/Linux
(sid_armhf-dchroot)praveen@abel:~$ 

Does this MR meet the acceptance criteria?

Conformity

• 📋 Does this MR need a changelog?
  • I have included a changelog entry.
  • I have not included a changelog entry because _____.
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team