chore: enable release-please & add it to CI

[weboko]

Problem

Right now it takes some time to make a release of @waku/* packages and it is mostly manual work that blocks other devs.

Solution

Considering different approaches release-please is the most convenient one.

Example of an automated PR for next release: #1157

Notes

Default mapping is used:
https://git.io/JqCZL
Description of config:
https://github.com/googleapis/release-please/blob/main/docs/manifest-releaser.md

• Resolves ci: automated release process #890

[weboko]

This is needed as starting point to create next versions. Description

[weboko]

I intentionally defined properties with default valued because they might be used by someone later.

[weboko]

btw it is a hash of a commit (not including) from which it will make next release

[github-actions]

size-limit report 📦

Path	Size	Loading time (3g)	Running time (snapdragon)	Total time
Waku core	133.54 KB (0%)	2.7 s (0%)	3.6 s (+0.64% 🔺)	6.2 s
Waku default setup	423.93 KB (0%)	8.5 s (0%)	8.9 s (+51.06% 🔺)	17.4 s
ECIES encryption	44.86 KB (0%)	898 ms (0%)	3.3 s (+31.95% 🔺)	4.2 s
Symmetric encryption	44.86 KB (0%)	898 ms (0%)	2.5 s (+15.87% 🔺)	3.3 s
DNS discovery	108.63 KB (0%)	2.2 s (0%)	3.7 s (+0.85% 🔺)	5.9 s
Privacy preserving protocols	132.54 KB (0%)	2.7 s (0%)	2.3 s (-40.06% 🔽)	4.9 s
Light protocols	134.55 KB (0%)	2.7 s (0%)	3.8 s (+52.83% 🔺)	6.5 s
History retrieval protocols	134.38 KB (0%)	2.7 s (0%)	2.9 s (-5.24% 🔽)	5.6 s

[fryorcraken]

another concern I have is around changelog management.

[fryorcraken]

@weboko. I guess this does not handle changelog at all, what are you thoughts on managing changelog?

[weboko]

@fryorcraken changelog is automatically updated based on commits.
Here is an example of release PR - #1157

[fryorcraken]

@weboko last remaining question: are we able to do patch increment only?

[weboko]

Right now it should be patch only.
Example - weboko/test-release...release-please--branches--weboko/test-release

[fryorcraken]

@weboko does it mean it releases for any change? or it only release for feat/fix ?

@weboko @danisharora099 I propose to make PR approval mandatory from this PR because it now directly release. Today we only patch increment but once we do minor and patch increment, we'll need a second pair of eye to ensure that we mark PR as breaking API when they do. Nothing worse than a lib with a patch bump that breaks backward compatibility. WDYT?

[weboko]

@weboko does it mean it releases for any change? or it only release for feat/fix ?

@weboko @danisharora099 I propose to make PR approval mandatory from this PR because it now directly release. Today we only patch increment but once we do minor and patch increment, we'll need a second pair of eye to ensure that we mark PR as breaking API when they do. Nothing worse than a lib with a patch bump that breaks backward compatibility. WDYT?

I agree, but in case a mistake will be made - we still can fix it in a release PR created by the bot.