Bump Bazel from 4.0.0 to 4.1.0 (#2024)

**What this PR does / why we need it**:
[v4.1.0](https://github.com/bazelbuild/bazel/releases/tag/4.1.0) got released last week. This release includes bazelbuild/bazel#12882, which fixes what we were facing; no longer needed to come with the workaround.

I've confirmed that it works fine without passing the workaround flag `--features=-debug_prefix_map_pwd_is_dot`.

**Which issue(s) this PR fixes**:

Fixes #1913

**Does this PR introduce a user-facing change?**:
<!--
If no, just write "NONE" in the release-note block below.
-->
```release-note
NONE
```

This PR was merged by Kapetanios.

.bazelrc

@@ -25,10 +25,6 @@ build --define DOCKER_REGISTRY=localhost:5000
 # https://github.com/bazelbuild/rules_docker/issues/842
 build --host_force_python=PY2
 
-# TODO: Remove the workaround flag after bumping Bazel to greater than 4.0.0
-# Workaround for this: https://github.com/bazelbuild/bazel/issues/12905
-build --features=-debug_prefix_map_pwd_is_dot
-
 # CI configurations
 build:ci --define DOCKER_REGISTRY=gcr.io/pipecd
 build:ci --remote_http_cache=https://storage.googleapis.com/pipecd-bazel-cache

.bazelversion

@@ -1 +1 @@
-4.0.0
+4.1.0