[openssl/openssl] 3e76b3: riscv: Clarify dual-licensing wording for GCM and AES

[openssl-machine]

  Branch: refs/heads/master
  Home:   https://github.com/openssl/openssl
  Commit: 3e76b388521ccafddd8ba19d9ab62c8d25e83e0c
      https://github.com/openssl/openssl/commit/3e76b388521ccafddd8ba19d9ab62c8d25e83e0c
  Author: Heiko Stuebner <heiko.stuebner at vrull.eu>
  Date:   2023-07-06 (Thu, 06 Jul 2023)

  Changed paths:
    M crypto/aes/asm/aes-riscv32-zkn.pl
    M crypto/aes/asm/aes-riscv64-zkn.pl
    M crypto/modes/asm/ghash-riscv64.pl
    M crypto/perlasm/riscv.pm

  Log Message:
  -----------
  riscv: Clarify dual-licensing wording for GCM and AES

The original text for the Apache + BSD dual licensing for riscv GCM and AES
perlasm was taken from other openSSL users like crypto/crypto/LPdir_unix.c .

Though Eric pointed out that the dual-licensing text could be read in a
way negating the second license [0] and suggested to clarify the text
even more.

So do this here for all of the GCM, AES and shared riscv.pm .

We already had the agreement of all involved developers for the actual
dual licensing in [0] and [1], so this is only a better clarification
for this.

[0] https://github.com/openssl/openssl/pull/20649#issuecomment-1589558790
[1] https://github.com/openssl/openssl/pull/21018

Signed-off-by: Heiko Stuebner <heiko.stuebner at vrull.eu>

Reviewed-by: Tim Hudson <tjh at openssl.org>
Reviewed-by: Paul Dale <pauli at openssl.org>
(Merged from https://github.com/openssl/openssl/pull/21357)