Feature/lit 2591 js sdk remove all redundantunused build processes and

[Ansonhkg]

Description

Remove all redundant/unused build processes and files.

before: 🫃
after: 😮‍💨

🚀 Features

• (gen:internal-dev) Improve script to avoid linting issue
• (tool) Add warning message to --fetch flag to update:contracts-sdk command

🐛 Bug Fixes

• (build) Linting when build:dev

🚜 Refactor

• (tool) Rename test:watch to test:unit:watch
• (tool) Rename test:bun with test:unit:bun and rename filename to unit-test-with-bun.mjs
• (tool) Remove publish:app:html command and build-html.mjs script
• (tool) Remove buildAndPublish command
• (tool) Remove bbp command
• (tool) Remove test:custom command & script
• (tool) Remove gen:demo command & script
• (tool) Remove gen:html command & related scripts
• (tool) Remove gen:react and scripts
• (tool) Remove outdated browser e2e tests & scripts
• (tool) Remove cypress completely
• (tool) Remove gen:nodejs command & scripts
• Remove lit-contracts dir
• (tool) Remove gen:contracts command
• (tool) Remove unused update:contracts command
• (tool) Remove delete:${?} commands & script
• (tool) Remove endisable-cache script & commands
• (tool) Remove dev & yalc commands & scripts
• (tool) Update command v to run script directly
• (tool) Remove npm:login command
• (tool) Remove b command
• (tool) Remove txServer command & scripts
• (tool) Remove apps commands & scripts
• (tool) Remove gen:config command
• (tool) Remove test_build.sh script
• (tool) Remove bun-link.sh script
• (tool) Remove dev file
• (tool) Remove unused --watch command
• (tool) Remove bump commands
• (package.json) Remove unused devDependencies
• (tool) Remove apps directory in favour of developer guide repo: https://github.com/LIT-Protocol/developer-guides-code/

📚 Documentation

• Remove unused consolelog-test

⚙️ Miscellaneous Tasks

• (build) Remove outdated gen:lib command
• Remove unused cypress.config.ts file
• (tool) Remove unused cloneFunc function
• Remove unused babel.config.json file

Type of change

• 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 style guidelines of this project
• I have performed a self-review of my 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
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules