Size IProfiler table based on info stored in SCC

[mpirvu]

The IProfiler hashtable is not resizable because it does not use any locks in order to limit overhead.
Bigger applications will create more IProfiler entries and the average length of the linked lists associated with the buckets in the IProfiler hashtable will increase, creating additional lookup overhead. On the other hand, creating too big of a spine for the IProfiler hashtable can lead to footprint increases.
This issue proposes to store a hint about the number of entries in the IProfiler table in the shared class cache. The subsequent JVMs can read the hint and create a correctly sized IProfiler table (assuming the the JVMs execute the same application/workload).