[fix] Ensure BLST_PORTABLE is 'y' during build on CI

Motivation and Context

Issue from steven_J on slack :

Hello I tried last ligo 1.0.0 and 0.73.0 today and got an illegal hardware instruction (core dumped) on an intel i5 the problem seems related to this old post: https://tezos-dev.slack.com/archives/CFX0B8Q3X/p1639246678302200

Description

To be sure that the BLST_PORTABLE is set to 'y' during build on the docker image, we setup it onto dockerfile.

Component

• compiler
• website
• webide
• vscode-plugin
• debugger

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Performance improvement (non-breaking change that improves performance)
• None (change with no changelog)

Changelog

Fix old processor can raise an illegal hardware instruction which can be raised with old processors. Avoid Tezos submodule emit ADX instructions.

Checklist:

• If a new syntax has been introduced, put a message on slack ligo-lsp
• Changes follow the existing coding style (use dune @fmt to check).
• Tests for the changes have been added (for bug fixes / feature).
• Documentation has been updated.
• Changelog description has been added (if appropriate).
• Start titles under ## Changelog section with #### (if appropriate).
• There is no image or uploaded file in changelog
• Examples in changed behaviour have been added to the changelog (for breaking change / feature).