And maybe this is because there is no clear definition of operation.
Use a paper and a pencil and do some drawings - we professionals need to do this, too.
* Schematic
* some kind of timing diagram where we see initial states, the key press signals and the LED signals..
First decision is do you want key to be just bounced in or in and out before you
act on the key press. That controls of course the program logic flow.
Generally speaking if you generate an interrupt on a pin edge or level, then start
a timer and set a flag. Set timer up to generate an interrupt when it is done, or poll it.
When timer finishes and you check that flag is set, and switch pin is still pressed, then
either perform the function needed or bounce it out/pin release and then perform function.
Best way is draw a flow diagram for your code, makes it easy to see and find where you have
not done everything necessary.
Many people use 50 mS or there abouts for bounce time, I have had switches bounce for
several hundred mS. That is your timer period. Note when you get first isr off pin you reset
and start the timer.
if you want to write code - it doesn´t care whether you are experienced or not - you need to have clear requirements. .. an idea how you want it to work.
Your requirements don´t depend on microcontroller or timer...
In your case it´s just a button and a LED...
You need to exactly desribe how the LED should work with repsect to button press .. and maybe your timing requirements.
A timing diagram could do. It is simple, just two lines. One for the button one for the LED to start with.
Then you may add some lines and text for timing and other information. Everyone in the world will understand - independent of language.
If you are not able to show what you want - nobody can help you ....
****
Function:
There are many ways for doing what you want.
You may do an internet search to find (maybe millions) examples, descriptions, code, schematics, timing diagrams...
Read through some of them .. then decide your own way to go.
There will be no 100% wrong, there will be no 100% right. Ask 10 engineers and get 10 different opinions.
Thus "your" way...not our or anyone else´s way