Remove runtime warning in snmpa_agent because of tuple fun usage
SNMP performance optimization
Merge branch 'lf/snmp-tuple-fun' into bmk/snmp/remove_tuple_fun/OTP-10672
[snmp/agent] Updated appup file
[snmp/agent] Proper copyright end year (2013)
[snmp] Updated release notes
Polish return values of snmpm_user_default according to snmpm_user doc

Even if not compliant with snmpm_user's doc, the previous return
values in snmpm_user_default were harmless because of how the
callbacks handle_trap and handle_report are called in snmpm_server.
[snmp/manager] Proper copyright end year (2013)
[snmp/manager] Updated release notes
[snmp/manager] Updated appup
Merge branch 'id/snmp_optimization' into bmk/snmp/manager/performance_improvement/OTP-10673
[snmp/manager] Proper copyright end year (2013)
[snmp/manager] Updated release notes
[snmp/manager] Updated appup
Merge branch 'bmk/snmp/snmp_user_default_return_values/OTP-10671' into bmk/snmp/snmp423_integration
Merge branch 'bmk/snmp/remove_tuple_fun/OTP-10672' into bmk/snmp/snmp423_integration

Conflicts:
	lib/snmp/doc/src/notes.xml
Merge branch 'bmk/snmp/manager/performance_improvement/OTP-10673' into bmk/snmp/snmp423_integration

Conflicts:
	lib/snmp/doc/src/notes.xml
ssl: Certificates and PEM-cache cleaning fixed to avoid memory leak

Certificate db cleaning messages where sent to the wrong process after
restructuring to avoid bottlenecks.

It is possible that the ssl manager process gets two cleaning messages
for the same entry. E.i. first cleaning message is sent and before it
is processed a new reference is allocated  and again released for the
entry, generating a second cleaning message.

Also in ssl_manger:handle_info/2 it is possible that there exists a
new reference to an "old" file name with a potential new content.
SSL: unify the different implementations signature check implementations

ssl_handshake and ssl_connection where doing essentially the same when
checking a public key signature. This unify both into a single function
SSL: simplify server key encoding, decoding and signature handling

server key encoding depends to the negotiated key exchange. Before
the encoding was limited to diffie-hellman keys. This changes allows
to select the key structure to decode and verify. It also consolidates
the transport encoding of the parameters into one place.