Improve packaging for publishing tasks

[ffoodd]

As you may read in how to publish your package on npm?, it's pretty easy to ignore dist/ folder from Git and still publish it to npm, by:

• ignoring dist/ from Git in the .gitignore file,
• adding dist/ folder to the npm package by adding it to the files entry in package.json.

This post also helps with pushing dist-tags, which could be handy for v3 (and soon v4).

[Lausselloic]

Maybe for npm package it's better to ignore dist on git repository, but need to check if composer package still work after that : https://packagist.org/packages/orange-opensource/orange-boosted-bootstrap

[ffoodd]

Nice catch, there're a lot to test (NuGet alongwith Composer, I guess).

FWIW, we might also use npm @scope to split Bootstrap's fork and Boosted custom things (TableSorter, Swiper, — and almost every custom components).

Needs to think about it :)

[ffoodd]

FWIW, the whole gh-pages publication task could probably be automated (mostly moving files, replacing strings, and probably using git subtree to do this from dev branch to gh-pages).

[ffoodd]

FYI: GitHub actions may be used to run npm publish → https://help.github.com/en/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages