Chore - Migrate react-native-render-html with history

[5ZYSZ3K]

This is a follow up to: #13, just made with a source branch from this repo, to b able to preview targeting PRs in one place

Description

This PR is meant to move the contents of react-native-render-html to this library with no other changes

Ultimately I decided to move packages/render-html and apps directories to the repo

• packages/render-html contains the core logic of react-native-render-html
• apps contains testing applications that may be helpful

I plan to create pull requests based off of this one to actually get it to work

References

Repository merge with history guide: https://gfscott.com/blog/merge-git-repos-and-keep-commit-history/
react-native-render-html repo: https://github.com/meliorence/react-native-render-html

Repository merge with history guide: https://gfscott.com/blog/merge-git-repos-and-keep-commit-history/
react-native-render-html repo: https://github.com/meliorence/react-native-render-html

[jsamr]

@5ZYSZ3K I converted to draft to make it clear this is a WIP. Please re-request for review when it's ready to be merged.

[5ZYSZ3K]

@jsamr there are still issues with bundling the website, but we decided to drop it for now. I think that I would try to release it in early alpha before christmas, so that we would have it prepared for a full major release which would take place in a new year

[jsamr]

@5ZYSZ3K That sounds absolutely reasonable 🙏🏻

[5ZYSZ3K]

@jsamr do you think you will be able to review it by monday?
And if not, would you mind if I tried make an alpha release from a branch?

And whatever the case: Is it okay if I would go ahead and create the package in npm, or do you want to do it yourself?

[5ZYSZ3K]

@jsamr I noticed only now, as I tried to get that merged to release the alpha version from main, that this github repository requires commits to be signed. Unfortunatelly I noticed that quite a few of them are not signed - I think that all of merge commits + some of those created by software mansion people.
What would you like to do about it? I think that I will be able to sign all of those commits by myself, but an easier approach would be to disable that rule. Do you have a preference or other ideas?

And we also realized that we should release render, transient-render-engine and css-processor together - is it ok to create an alpha release for all three of them?

[5ZYSZ3K]

@jsamr Just to let you know: I've been trying to get the alpha release from the branch, but it seems like our release-it config is no longer valid, it fails to get that released because of workspaces. I'll probably give it another shot after christmas, and I'll probably ask for help from someone who has experience with this