Inconsistent subassembly object ID for different sizes of size_t

[clonker]

Description

When compiling solc for different sizes of size_t, e.g., comparing emscripten and linux builds, the object ID of subassembly paths as determined here

solidity/libevmasm/Assembly.cpp

Line 1825 in a652292

size_t objectId = std::numeric_limits<size_t>::max() - m_subPaths.size();

will be inconsistent between the two builds. This potentially leads to inconsistent assembly text between emscripten and native 64 bit builds.

We should test the precise impact this has and fix it to the 64 bit behavior.