Changelog Verification CI failed for First GA packages

[kazrael2119]

We have two first GA release this week:
#30012
#30154
but both of them get failed on Changelog Verification check in pipeline with the error message

Usually, if a package is going to be first GA, the changelog will be

# Release History
    
## 1.0.0 (2024-06-24)

The package of @azure/arm-resourcesdeploymentstacks is using our next generation design principles. To learn more, please refer to our documentation [Quick Start](https://aka.ms/azsdk/js/mgmt/quickstart).

which doesn't have any code details.
not sure whether a first beta package will trigger this error too.

cc @qiaozha @MaryGao

[MaryGao]

The message told you the error:

##[error]The changelog entry did not contain any of the recommended sections (Features Added, Breaking Changes, Bugs Fixed, Other Changes), please add at least one. See https://aka.ms/azsdk/guideline/changelogs for more info.

##[error]PowerShell exited with code '1'.

I prefer to change to something like below:

# Release History
    
## 1.0.0-beta.1 (2024-06-24)

### Features Added

The package of @azure/arm-resourcesdeploymentstacks is using our next generation design principles. To learn more, please refer to our documentation [Quick Start](https://aka.ms/azsdk/js/mgmt/quickstart).

For GA:

# Release History
    
## 1.0.0 (2024-06-24)

### Features Added

This is the first GA for @azure/arm-resourcesdeploymentstacks and the package is using our next generation design principles. To learn more, please refer to our documentation [Quick Start](https://aka.ms/azsdk/js/mgmt/quickstart).

[qiaozha]

Normally feature added means minor change, but GA/preview track2 maybe Modular when MPG is ready is not.
but if we call it breaking change, it would be weird if we don't show them what is breaking.

[qiaozha]

@joheredi @xirzec Could you help share your insights here? Thank you

[xirzec]

Seems like enforcement was recently changed to block on this: Azure/azure-sdk-tools#8463

"Features Added" is probably the most correct thing to use, and appears to be what others have used for the initial release: https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/openai/Azure.AI.OpenAI/CHANGELOG.md#100-beta1-2023-02-06

Perhaps we could make the check smarter about not enforcing recommended sections on the first release though? @weshaggard

[weshaggard]

The guidelines have always listed having a required section heading however we recently discovered a bug which didn't correctly fail the validation step, which has been fixed.

I don't think we need to special case new releases we should use "Features Added" for those cases.

[wanlwanl]

FYI, current state here: Azure/azure-sdk-tools#8487