Add Support for subsectioned Values

[Haepaxlog]

This PR closes #193 by adding section info to necessary structs and also retrieving
this section mapping through # @section -- [section name] annotations.

In order to keep compatibility with regular unsectioned values.yaml files, this means also
introducing a separate Sections field to chartTemplateData , through which a template
similar to valuesTableTemplate called valuesTableSectionedTemplate can be evoked to generate
files similar to this:

## Values

### General
| Key | Type | Default | Description |
|-----|------|---------|-------------|
| controller.extraVolumes[0].name | string | `"config-volume"` |  |
| controller.image.repository | string | `"nginx-ingress-controller"` |  |
| controller.image.tag | string | `"18.0831"` |  |
| controller.name | string | `"controller"` |  |
| controller.service.annotations."external-dns.alpha.kubernetes.io/hostname" | string | `"stupidchess.jmn23.com"` | Hostname to be assigned to the ELB for the service |
| controller.service.type | string | `"LoadBalancer"` |  |

### Some Section
| Key | Type | Default | Description |
|-----|------|---------|-------------|
| controller.extraVolumes[0].configMap.name | string | `"nginx-ingress-config"` | Uses the name of the configmap created by this chart |
| controller.persistentVolumeClaims | list | the chart will construct this list internally unless specified | List of persistent volume claims to create. |
| controller.podLabels | object | `{}` | The labels to be applied to instances of the controller pod |

### Special Attention
| Key | Type | Default | Description |
|-----|------|---------|-------------|
| controller.ingressClass | string | `"nginx"` | You can also specify value comments like this |
| controller.publishService | object | `{"enabled":false}` | This is a publishService |
| controller.replicas | int | `nil` | Number of nginx-ingress pods to load balance between |

or HTML data:

General

Key	Type	Default	Description
controller.extraVolumes[0].name	string	"config-volume"
controller.image.repository	string	"nginx-ingress-controller"
controller.image.tag	string	"18.0831"
controller.name	string	"controller"
controller.service.annotations."external-dns.alpha.kubernetes.io/hostname"	string	"stupidchess.jmn23.com"	Hostname to be assigned to the ELB for the service
controller.service.type	string	"LoadBalancer"

Some Section

Key	Type	Default	Description
controller.extraVolumes[0].configMap.name	string	"nginx-ingress-config"	Uses the name of the configmap created by this chart
controller.persistentVolumeClaims	list	the chart will construct this list internally unless specified	List of persistent volume claims to create.
controller.podLabels	object	{}	The labels to be applied to instances of the controller pod

Special Attention

Key	Type	Default	Description
controller.ingressClass	string	"nginx"	You can also specify value comments like this
controller.publishService	object	{ "enabled": false }	This is a publishService
controller.replicas	int	null	Number of nginx-ingress pods to load balance between

I'd be happy if this feature makes it in in some shape or form as I can see the need for documentation people to have it integrated into the tool :)

[klaudiagrz]

@Nepo26 any chances of implementing this feature in the near future? Looks super helpful!

[Nepo26]

Hi @klaudiagrz,

It really seems promising, I just need to review it, but I'm with little time recently. I can't promise anything, however I'll try to focus some time in this weekend.

[Nepo26]

Got some time now. I'm looking into it.

[kenrick-tan-partior]

Hey @Nepo26, did you manage to look at this PR yet? :)

[norwoodj]

Hey @Haepaxlog I'm sorry for the slow response on this. I really like the idea here, and I've added some comments that I think would improve things slightly. Thanks so much for the contribution, if you make the couple changes I've proposed, happy to merge it.

[ksputo]

hey @norwoodj , could you please have a look at the changes? Thank you 🙇

[norwoodj]

Sorry for my slowness getting back to this. I've merged. Thank you very much for the very cool contribution