Create a process for package bug fixes and customisations.

[tachyons]

We are currently using https://github.com/CircuitVerse/packages to update packages on our end. This is not ideal due to multiple reasons.

1. We won't get security fixes from upstream quickly, we need to do that manually
2. It is difficult to keep track of the changes we made
3. Rebasing get harder with time

My suggestions are to

1. Create a list of changes we had to make and keep that list updated for each MR
2. Create PR to upstream to Each change and link that PR in the above list
3. If the package is abandoned, consider switching to another package which provides the same functionality

[manjotsidhu]

@aman-singh7 Can we do a test using official packages again to verify if they have fixed the issues we faced regarding inline builders. If it works now, then we are better off using official packages

[aman-singh7]

Cool 👍 I will test with the official package and let you know.