Design an architecture to avoid doing describe calls every time the extension is opened

[espl-saket]

• Currently, the extension does the REST callouts to Salesforce APIs to get the object describe information every time it has been opened
• Due to the limitations on the number of API callouts that can be made to SF per day, and considering that other applications in the org would also be using up the callouts, it is necessary to design an effective and a faster way to fetch the information
• Possible approaches include storing the details per-org in the browser storage using a key-value pair that stores the org ID as the key and the describe information as the value