Remove default ingress annotation from helm chart so that ingressClassName is settable in wrapped chart

[rlaveycal]

Description

Remove the default ingress annotation that defaults to nginx. ingressClassName is the correct way to set the ingress.

Why is this needed?

Fixes #1000

When the chart is wrapped inside another it is not possible to unset the ingress annotation (see helm/helm/issues/9027). This means that if ingress.ingressClassName is set the deployment fails due to the annotation also being present.

Who is this for?

We are StructureFlow.

How Has This Been Tested?

I've successfully deployed my local change to a local cluster with the ingress enabled and ingressClassName: nginx

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have signed-off my commits with git commit -s
• I have added tests to cover my changes.
• All new and existing tests passed.

[derek]

Thank you for your contribution. It seems that one or more of your commits have a "Signed-off-by" statement with an anonymous email address. The Developer Certificate of Origin (DCO) requires all commits to be signed off by genuine, contactable individuals. Please see our contributing guide.

### :bulb: Shall we fix this?

This will only take a few moments.

First, clone your fork and checkout this branch using the git CLI.

Next, set up your real name and email address:

git config --global user.name "Your Full Name"
git config --global user.email "[email protected]"

Finally, run one of these commands to add the "Signed-off-by" line to your commits.

If you only have one commit so far then run: git commit --amend --signoff and then git push --force.
If you have multiple commits, watch this video.

Check that the message has been added properly by running "git log".