ci(*): release notes automation

[clukhei]

Automating release notes generation right after publish has completed for latest tag

Segregation of release notes to feat, refactor, fix

PR title should always be in conventional commit format. Component name should be in pascal case

E.g fix(Button): description

Breaking change --> add exclamation
E.g feat(ComboBox): removal of prop menu list !

✏️ Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

🧪 How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B

✅ Checklist:

• My code follows the SGDS style guidelines and naming conventions
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• Any dependent changes have been merged and published in downstream modules