Eliminate obligatory using of `html/template` and give control to user

[yznts]

Need to provide something like ImplementsRender interface. This interface will give rendering control to page/component.
Steps to implement:

• Define new interface for implementing render
• Remove obligatory Template method in page interface
• Define new interface for optional Template method
• Integrate manual rendering control into lifecycle (check for at least one rendering option must to be implemented)

Pros:

• Giving developer a control over final rendering step
• Eliminating obligatory html/template usage, developer can choose alternative ways like maragudk/gomponents
• Keeping components templates/rendering inside of *.go files will allow to distribute component libraries with Go packages

[yznts]

Explore possibility of using tinygo compiler

[yznts]

tinygo has somef limitations:

• net/http is not supported
• html/template and text/template are not supported

So, using Render function instead of Template will be a requirement for using tinygo. Also, all references to html/template must to be excluded from the library code. As an option, we can use build tag notemplates to exclude html/template functionality from build. kyoto needs deep restructurization and templates separation to support tinygo, so changes in this direction will be done step-by-step.