Critical Bug Report: fireSectionChange() Method Not Returning Updated GPP String in Version 3.1.5

[ankitonetrust]

In version 3.1.5 of the IAB GPP library, the method fireSectionChange() does not return the updated or correct GPP string after modifying a section. This issue was not present in version 3.1.2, where the method worked as expected.

Steps to Reproduce
Update to GPP library version 3.1.5.
Call fireSectionChange() after making changes to a section in the GPP configuration.
Check the returned GPP string — it does not reflect the updated state.

Expected Behavior
The fireSectionChange() method should return the correct and updated GPP string, incorporating any changes made to the relevant sections.

Actual Behavior
The GPP string returned by fireSectionChange() is outdated or incorrect and does not reflect the recent changes to the section.

Environment
Library Version: 3.1.5
Previous Working Version: 3.1.2
Environment: [e.g., Node.js, Browser, etc.]

Additional Information
This issue was not observed in version 3.1.2, where the fireSectionChange() method worked as intended.
The problem seems to arise specifically with the updated library in version 3.1.5.

Suggested Priority
High — This issue breaks functionality for applications relying on fireSectionChange() to dynamically update and retrieve the correct GPP string.

`import { GPP } from '@iabgpp/core';

// Example showing the issue
const gpp = new GPP();
gpp.setSection('sectionId', { key: 'value' });

const updatedGppString = gpp.fireSectionChange('sectionId');
console.log('Updated GPP String:', updatedGppString); // Not reflecting the changes in version 3.1.5
`