Linux/ARM: Regression fix in release build since "UNW_ARM_UNWIND_METHOD=6" (dotnet...

Linux/ARM: Regression fix in release build since "UNW_ARM_UNWIND_METHOD=6" (dotnet/coreclr#5126)

> https://github.com/dotnet/coreclr/pull/3502/
>   Fix Stack Unwind Behavior of Libunwind-ARM

We have been getting the 300+ failures(in ./JIT/ directory) in release-build
mode whenever we have always run CoreCLR unit-test since
https://github.com/myungjoo/coreclr/commit/dotnet/coreclr@35b5df6888f1574e6ef9313c6bc8522d1817573d.
(Reference - https://wiki.linaro.org/KenWerner/Sandbox/libunwind#overhead_of_the_ARM_specific_unwind-tables)

With recent fixes on stack unwindings, it appears that we no more send ambiguous
requests to libunwind-arm.(Checked by @myungjoo, with cases of dotnet/coreclr#3462)

From now on, let's remove the unwind environment variable (e.g., UNW_ARM_UNWIND_METHOD=6)

Signed-off-by: Geunsik Lim <geunsik.lim@samsung.com>
Acked-by: MyungJoo Ham <myungjoo.ham@samsung.com>
CC: Ben Pye <@benpye>
CC: Jan Kotas <@jkotas>
CC: Matt Mitchell <@mmitche>
Commit migrated from https://github.com/dotnet/coreclr/commit/3351bfc78dccbc161ab055883cdb6b7bb3df3c67