Update to omniscidb 5.5.0

[pearu]

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 just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[pearu]

@jclay @andrewseidl @xmnlab please review.

Once this PR is merged, the plan is to update #22 to enable pyomniscidb as well.

[xmnlab]

note: maybe if we have this constraint < 12 constantly, we could change it (in the future) to a variable (maybe LLVM_UNSUPPORTED_VERSION or something similar) and we could just change the variable value when needed.

[pearu]

I would hope that at some point we could remove the constraint on the LLVM version altogether. Meanwhile, maintaining it within the meta.yaml is straightforward, and adding the extra boilerplate is not worth it, IMHO.

[xmnlab]

LGTM! thank you @pearu