ord: Set Tech name when using Tech API programmatically

[mikesinouye]

Summary

When using the Tech API programmatically, the tech lef name will not be set when creating a tech. This change aligns the API with the tcl proc, which passes the tech name when creating the tech. Extend the existing Tech API test to verify this.

OpenROAD/src/OpenRoad.tcl

Lines 30 to 38 in f6aef4a

	set tech_name ""
	set lib_name [file rootname [file tail $filename]]
	if { [info exists keys(-tech_name)] } {
	set tech_name $keys(-tech_name)
	} elseif { $make_tech } {
	set tech_name $lib_name
	}
	ord::read_lef_cmd $filename $lib_name $tech_name $make_tech $make_lib

Type of Change

• Bug fix

Impact

Tech name can now be set when using Tech API.

Verification

• I have verified that the local build succeeds (./etc/Build.sh).
• I have run the relevant tests and they pass.
• My code follows the repository's formatting guidelines.
• I have signed my commits (DCO).

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[gemini-code-assist]

Code Review

This pull request updates the Tech::readLef function in src/Tech.cc to conditionally assign a technology name based on the make_tech flag, ensuring the library name is used when a technology is being created. A corresponding assertion was added to the timing_report_api.py test to verify that the technology name is correctly initialized and not empty. I have no feedback to provide.