Add create licence supplementary years service

[Beckyrose200]

https://eaflood.atlassian.net/browse/WATER-4588
#1236

The new two-part tariff supplementary bill run requires licences to be recorded in our new LicenceSupplementaryYears table, along with the years they affect. The first ticket we picked up for this new process was amending the existing annual two-part tariff review pages. A licence can be removed from the bill run there and this should be flagged. This was added to the existing review page journey. Since starting work on the other flagging tickets it became clear that the process of adding the licence into our LicenceSupplementaryYears table is going to be repeated if we don't pull this out into its own service. So that is what this PR is for, making a service just for creating the licence record that can be shared amongst the various ways a licence can be flagged.

[Beckyrose200]

Just a note, on the service I have resorted to creating a private fetch function to look for any existing records with the same properties that we want to persist. We did discuss using a where clause on the query insert, but after some research, I don't think this is possible due to the where clause only being used for 'selects', 'updates', and 'deletes'. I could not find any examples in our code that have a where clause on an insert.

I also looked into the option of using onConflict however, this again was a no-go due to the fact the database itself needs to have constraints on the table for the onConflict to be triggered. Any suggestions on this let me know :)

[Cruikshanks]

Just a note, on the service I have resorted to creating a private fetch function to look for any existing records with the same properties that we want to persist. We did discuss using a where clause on the query insert, but after some research, I don't think this is possible due to the where clause only being used for 'selects', 'updates', and 'deletes'. I could not find any examples in our code that have a where clause on an insert.

I also looked into the option of using onConflict however, this again was a no-go due to the fact the database itself needs to have constraints on the table for the onConflict to be triggered. Any suggestions on this let me know :)

My bad. It can be done in raw SQL or by dropping down to Knex, but it would be pretty messy. We don't need to optimise this, so don't worry about it!

[Cruikshanks]

Just some suggested tweaks.

[Cruikshanks]