chore(endpoint): added empty checks

[ivankatliarchuk]

What does it do ?

I captured, that even for 0 properties, there is an improvement if we use Map vs Slice. Reason

• The speedup is consistent (1.38-1.40x) across all endpoint counts, confirming it's a per-lookup constant overhead, not algorithmic complexity.

So I've added empty check to avoid lookups for specific cases.

if len(e.ProviderSpecific) == 0 {
		.......
	}

To make sure when ZERO properties, Slice and Map behave same way now

The final implementation:

• GetProviderSpecificProperty: len check + slice iteration
• SetProviderSpecificProperty: slice iteration + append
• DeleteProviderSpecificProperty: len check + slice iteration + remove

Motivation

Benchmark results #6156
Map or Slice #5814

More

• Yes, this PR title follows Conventional Commits
• Yes, I added unit tests
• Yes, I updated end user documentation accordingly

[coveralls]

Pull Request Test Coverage Report for Build 21543296792

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 31 unchanged lines in 2 files lost coverage.
• Overall coverage increased (+0.008%) to 79.185%

---

Files with Coverage Reduction	New Missed Lines	%
openshift_route.go	1	84.21%
endpoint.go	30	86.36%

Totals
Change from base Build 21510752750:	0.008%
Covered Lines:	16073
Relevant Lines:	20298

---

💛 - Coveralls

[szuecs]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: szuecs

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [szuecs]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[vflaux]

/lgtm