config: Convert process.rlimits from an array to an object

[wking]

Rlimits do not need either ordering or repeat entries for a single type. While come JSON libraries preserve object key order or allow repeats, there are many JSON libraries which do not (e.g. Python and JavaScript both parse JSON objects into hash tables). Using objects here reinforces the unimportance of ordering or repeated entries.

Also add Solaris support. I'm not entirely clear on this, because while Solaris is POSIX-certified system and there is a Solaris man page for setrlimit, @anuthanclaims no Solaris support for rlimits.

The additionalProperties object bit comes from here, although it is not documented in draft 4 of the JSON Schema RFC.

[crosbymichael]

uhh, just because order is not important does not mean you have to change the schema

[wking]

On Tue, Sep 27, 2016 at 09:04:54AM -0700, Michael Crosby wrote:

uhh, just because order is not important does not mean you have to
change the schema

True, but using an array means entries are referenced by index
(e.g. ‘rlimits[0]’, but I think validation output would be easier to
read if they were referenced by resource (e.g.
‘rlimits["RLIMIT_CORE"]’). opencontainers/runtime-tools#223 is
currently (with opencontainers/runtime-tools@f175fae0) using the
resource in validation error messages 1, which assumes there will be
no duplicates. I'd rather make that an explicit requirement, and
converting to an object here sets us up for that (I've just filed #584
with the other half of making that explicit).

[mrunalp]

Closed by #607