Increase the size of the script editor breakpoint gutter's clickable area

[Gigabitten]

Describe the project you are working on:
I am working on a simple game where you're a frog and you hop around and stick to surfaces and stuff.

Describe the problem or limitation you are having in your project:
Figuring out how to use breakpoints is unintuitive. Apparently you can press F9 or put the word "breakpoint" or click in the region to the left of a line, but there's no immediately apparent UI option under debug for it, and the region to click is very narrow.

Describe the feature / enhancement and how it helps to overcome the problem or limitation:
Improve the size and positioning of the region to press to put down a breakpoint so that it's consistent with other editors, add a UI option or a tooltip somewhere obvious or something, and probably update the documentation as well with this functionality.

Describe how your proposal will work, with code, pseudocode, mockups, and/or diagrams:

------------        -----
| O        |   ->   | O |
------------        -----

If this enhancement will not be used often, can it be worked around with a few lines of script?:
It can be worked around with zero, but this is just a good design thing.

Is there a reason why this should be core and not an add-on in the asset library?:
Same answer as the last one. It's just better design.

Sorry if this seems a bit silly, but I really did have trouble figuring out how to make a breakpoint at all since you seriously have to click on the left third of the box to get it to activate, and although there's some pretty detailed documentation on the basics of debugging, it doesn't once mention how to actually make a breakpoint. Figured I'd take the time to put this in, even if it is quite a small fix for the amount of typing I need to do.

[Jummit]

(Kinda) Duplicate of #533

[KoBeWi]

IMO the clicking region isn't that bad, because the cursor changes when you hover over it.

[Gigabitten]

IMO the clicking region isn't that bad, because the cursor changes when you hover over it.

This is both very easy to change and only causes benefits if changed. Besides, you're not looking at this from the perspective of a new user who is trying to learn to use the interface.