Improve folder name to reflect on the actual version of the package

[sajjaphani]

In core-plans, we have some package names which I feel are misleading.

• boost159
• postgresql11
• postgresql93

For example, boost159, which is a pinned version of 1.59. A better folder name could be boost@1.59.

The idea is to use the pinned version reflect in the name of the package followed by @ sign.
<name>@<major.minor.patch>

Below table shows some suggestions for the old and new folder names:

Old Name	New Name
bdwgc7	bdwgc@7
bdwgc8	bdwgc@8
boost159	boost@1.59
clang7	clang@7
corretto11	corretto@11
corretto8	corretto@8
curator4	curator@4
elasticsearch5	elasticsearch@5
ffmpeg3	ffmpeg@3
ffmpeg4	ffmpeg@4
ghc710-bootstrap	ghc-bootstrap@7.10
ghc710	ghc@7.10
ghc80	ghc@8.0
ghc82-bootstrap	ghc-bootstrap@8.2
ghc82	ghc@8.2
ghc84	ghc@8.4
ghc86	ghc@8.6
ghc88	ghc@8.8
gnupg2	gnupg@2
gradle4	gradle@4
gradle5	gradle@5
gtk2	gtk@2
haproxy16	haproxy@1.6
haproxy17	haproxy@1.7
haproxy18	haproxy@1.8
haproxy19	haproxy@1.9
haproxy20	haproxy@2.0
haproxy21	haproxy@2.1
icu52	icu@52
icu56	icu@56
kafka2	kafka@2
llvm7	llvm@7
logstash2	logstash@2
node10	node@10
node11	node@11
node12	node@12
node14	node@14
node6	node@6
openssl11	openssl@1.1
postgresql11-client	postgresql-client@11
postgresql12-client	postgresql-client@12
postgresql13-client	postgresql-client@13
postgresql93-client	postgresql-client@9.3
postgresql94-client	postgresql-client@9.4
postgresql95-client	postgresql-client@9.5
postgresql96-client	postgresql-client@9.6
prometheus1	prometheus@1
prometheus2	prometheus@2
python2	python@2
python34	python@3.4
python36	python@3.6
python37	python@3.7
python38	python@3.8
python39	python@3.9
redis3	redis@3
redis4	redis@4
ruby25	ruby@2.5
ruby26	ruby@2.6
ruby30	ruby@3.0
tomcat7	tomcat@7
tomcat8	tomcat@8

Currently, plan builder does not allow us to use any special characters in the package name. But changing the folder names still improves the clarity of the version of the package on a high level.

Note: This change does not require us to change the contents of the plan file. We only need to update the plan file path in the builder.
Follow a similar pattern for the packages in chef-base-plans org.

[mwrock]

Also need to update the path in the .bldr.toml