Support providing relative paths to configuration file

[patmuk]

Changes

fixes #2166

Checklist

• An issue to be fixed by this PR is listed above.
• New tests are added to ensure new features are working. Please refer to this page to see how to add a test.
• ./frb_internal precommit --mode slow (or fast) is run (it internal runs code generator, does auto formatting, etc).
• If this PR adds/changes features, documentations (in the ./website folder) are updated.
• CI is passing. Please refer to this page to see how to solve a failed CI.

Remark for PR creator

• ./frb_internal --help shows utilities for development.
• If fzyzcjy does not reply for a few days, maybe he just did not see it, so please ping him.

[fzyzcjy]

Looks great! Maybe we can fix the CI by changing what it complains, e.g.

diff --git a/frb_example/flutter_via_create/pubspec.lock b/frb_example/flutter_via_create/pubspec.lock
index eadc974..ad3f38c 100644
--- a/frb_example/flutter_via_create/pubspec.lock
+++ b/frb_example/flutter_via_create/pubspec.lock
@@ -297,10 +297,10 @@ packages:
     dependency: transitive
     description:
       name: web
-      sha256: d43c1d6b787bf0afad444700ae7f4db8827f701bc61c255ac8d328c6f4d52062
+      sha256: cd3543bd5798f6ad290ea73d210f423502e71900302dde696f8bff84bf89a1cb
       url: "https://pub.dev/"
     source: hosted
-    version: "1.0.0"
+    version: "1.1.0"
   webdriver:
     dependency: transitive
     description:

[patmuk]

Thanks :)
Yes - I have the same "problem" in my other PR. I think that locally the dependencies are getting updated, while on CI they are compared to the old once. Note that the pubspec.yaml isn't changed - the new versions are still valid.
Thus it is very likely that a user's local system would update as well.

I think it would be best to use the new pub spec.locks - but I did not look into the CI config to see how/why it compares with the old ones.

But I don't have a strong opinion on that, I could revert the pubspec.lock's to the older state as well.

[fzyzcjy]

I think it would be best to use the new pub spec.locks - but I did not look into the CI config to see how/why it compares with the old ones.

Without detailed exploration, my first guess: because the flutter version is locked

[patmuk]

I think it would be best to use the new pub spec.locks - but I did not look into the CI config to see how/why it compares with the old ones.

Without detailed exploration, my first guess: because the flutter version is locked

Oh, that is very likely! I will revert the podspec.locks.

[patmuk]

Ah, actually no one of us committed any pubspec.lock files.

I guess that there is just a new package of "web"available (1.0.0 -> 1.1.0) the build process updated to?

[fzyzcjy]

Yes I think so