erp5_oauth2_authorisation: Store more HTTPResponse headers using setHeader

During the response process (especially setBody), HTTPResponse accesses
and updates some response headers in its "headers" property (a dictionary).
addHeader puts the response headers in a list which will not be updated by
HTTPResponse. This is "more correct" from an RFC perspective, as any header
specified as being a sequence of values delimited by commas may be split
among multiple headers.
So, keep using addHeader by default, but special-case some headers which
are accessed and must be successfully updated by HTTPResponse itself so
that those headers are set using setHeader, which updates the "headers"
property.
15 jobs for master in 0 seconds
Status Job ID Name Coverage
  External
failed ERP5.CodingStyleTest-Master

01:00:05

failed ERP5.PerformanceTest-Master

00:27:39

failed ERP5.UnitTest-Master

01:35:53

failed ERP5.UnitTest-Zope2

01:59:07

passed SlapOS.Eggs.UnitTest-Master.Python2

00:16:22

passed SlapOS.Eggs.UnitTest-Master.Python3

00:19:50

passed Wendelin.UnitTest-Master

00:58:00

failed ERP5.CodingStyleTest-Master

00:45:57

failed ERP5.PerformanceTest-Master

00:28:02

failed ERP5.UnitTest-Master

01:52:41

failed ERP5.UnitTest-Zope2

03:19:48

passed SlapOS.Eggs.UnitTest-Master.Python2

00:17:58

passed SlapOS.Eggs.UnitTest-Master.Python2

00:15:51

passed SlapOS.Eggs.UnitTest-Master.Python3

00:19:10

passed SlapOS.Eggs.UnitTest-Master.Python3

00:17:52