Switch to use double as datatypes and rename package to libccd-double

[traversaro]

Implement the idea described in #4 .
I also added a run_constrained condition to ensure that libccd and libccd-double conflict.
I also bumped the build number, strictly speaking it is not necessary but I think it may avoid confusions.
I also added myself to mantainers.

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• requirements: run_constrained: libccd < 1 should not contain a space between relational operator and the version, i.e. libccd <1

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[traversaro]

@conda-forge-admin, please restart ci

[traversaro]

@conda-forge-admin, please rerender

[traversaro]

@conda-forge/ccd the PR is ready fo review.

[traversaro]

@conda-forge/ccd the PR is ready fo review.

Damn, the mention was wrong, the correct one is @conda-forge/libccd (let's also mention @wolfv just to be sure).

[traversaro]

Thanks!