Implemented v8

[rcaferati]

•	Package renamed for v8 to the scoped npm package: @rcaferati/react-awesome-button (old unscoped package remains v7 line).
•	package.json updated for scoped publishing:
•	name → @rcaferati/react-awesome-button
•	publishConfig.access → public
•	dependencies/devDependencies reviewed (@rcaferati/wac kept as runtime dependency; Storybook/Lucide moved to dev-only)
•	exports / entrypoints / files verified for dist publishing
•	README fully refreshed to match current v8 patterns:
•	scoped install/import examples
•	corrected CSS import paths
•	corrected theme usage (themeBlue?.default ?? themeBlue)
•	corrected icon-only pattern (before prop, not children)
•	corrected AwesomeButtonProgress usage (onPress(event, next) + next(true|false))
•	corrected AwesomeButtonSocial behavior and sharer examples
•	outdated/incorrect props/examples removed/replaced
•	Storybook icon docs refactored into separate stories (under src/stories/icons/) for:
•	AwesomeButton
•	AwesomeButtonProgress
•	AwesomeButtonSocial
•	Lucide icon showcase patterns corrected:
•	blue theme cssModule loaded the same way as component stories
•	one-item-per-line layout for better mobile/small-screen scaling
•	icon-only buttons use before with no children
•	progress stories complete correctly (no infinite loading / no fake loading prop)
•	social examples updated to GitHub + Instagram (not email), and sizes include small/medium/large/auto
•	GitHub Pages Storybook deploy workflow added/reviewed (deploy-storybook.yml)
•	includes actions/configure-pages
•	builds Storybook and deploys to Pages
•	npm publish workflow added/reviewed (publish-npm.yml)
•	publishes on v* tags (and supports manual trigger)
•	checks tag/version match
•	uses npm publish --access public
•	builds/tests before publish
•	Public API export file (src/index.ts) reviewed
•	exports aligned with the intended v8 API (AwesomeButton, AwesomeButtonProgress, AwesomeButtonSocial + types)
•	Release process clarified
•	pushing package.json version alone does not publish
•	publish happens on pushed tags (e.g. v8.0.0) or manual workflow dispatch
•	Post-launch npm migration plan defined
•	deprecate old react-awesome-button v7 line with a message pointing users to @rcaferati/react-awesome-button