recipe/certificate_authority: use UTF-8 for CA certificate

The CertificateAuthority tool in ERP5 uses UTF8 encoding for certificates,
but by default OpenSSL does not. This cause an error when using non-ascii
characters:

```
The localityName field is different between CA certificate and the request
```

To solve the problem, the Certificate Authority recipe should use the same
encoding as ERP5, which requires adding `-utf8` option when invoking
OpenSSL.

For instance, creating a certificate with `localityName` Москва
will give the following with the default OpenSSL encoding:
`\C3\90\C2\9C\C3\90\C2\BE\C3\91\C2\81\C3\90\C2\BA\C3\90\C2\B2\C3\90\C2\B0`.

UTF8-encoding this same string gives `\D0\9C\D0\BE\D1\81\D0\BA\D0\B2\D0\B0`,
which is what ERP5 expects.
Status Job ID Name Coverage
  External
running SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

244:41:15

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

22:02:35

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

12:10:18

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

11:54:06

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

21:54:56

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

20:44:22

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

14:50:37

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

12:05:20

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

09:20:15

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

11:41:00

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

07:40:52

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

28:19:10

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

23:43:54

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

22:28:29

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

16:04:04

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

20:36:36

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

16:08:52

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

10:57:55

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

22:21:38

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

24:11:43

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

27:38:05

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

19:59:57

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

15:44:37

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

12:04:50

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

16:08:57

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

15:45:11

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

16:06:39

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

28:13:06

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

08:03:08

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

20:10:36

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

16:10:01

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

08:05:43

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

17:02:20

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

20:09:46

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

19:29:37

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

19:22:27

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

19:58:38

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

12:06:17

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

28:53:41

failed SlapOS.SoftwareReleases.IntegrationTest-Titouan.TestRunner.Dodo

18:57:51